Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.7
    • Component/s: Java Client
    • Labels:
      None

      Description

      The following is a proposal for temp queue naming.

      Currently our temp queue naming is hard coded to "Temp_ " + uuid.
      We could change this to a format that is configurable and captures more useful information that can be utilized by,

      a) management tools to provide more visibility
      b) ACL modules.

      I propose the following format

      {host}

      .

      {port}

      .

      {user_prefix}.{uuid}.

      The above format is configurable with {uuid} being the only mandatory part.
      The order of the tokens could also be changed.
      The scheme can be set globally using a jvm argument or per connection using connection URL.

      Example.{user_prefix}

      _

      {uuid}

      = Temp_535fewfsgdsg where user_prefix = "Temp"

        Activity

        Hide
        Rajith Attapattu added a comment -

        While there was agreement on the format there was no concensus about whether this should be configurable or not.
        The discussion on the mailing list is capture in this thread.
        http://markmail.org/search/?q=Qpid%20temp%20queue#query:Qpid%20temp%20queue+page:1+mid:nhp7it7tidg3hyjr+state:results

        I am just parking the patch over here for future reference.
        This patch was done against rev 700887 on Qpid trunk.

        Show
        Rajith Attapattu added a comment - While there was agreement on the format there was no concensus about whether this should be configurable or not. The discussion on the mailing list is capture in this thread. http://markmail.org/search/?q=Qpid%20temp%20queue#query:Qpid%20temp%20queue+page:1+mid:nhp7it7tidg3hyjr+state:results I am just parking the patch over here for future reference. This patch was done against rev 700887 on Qpid trunk.
        Hide
        Rob Godfrey added a comment -

        This patch has not been applied and thus is not part of M4. We should revisit this topic at a later date.

        Show
        Rob Godfrey added a comment - This patch has not been applied and thus is not part of M4. We should revisit this topic at a later date.
        Hide
        Rajith Attapattu added a comment -

        There was no consensus on a scheme to configure temp queues by default.
        However with the new addressing syntax it's now possible for a user to name a temp queue subject to the limitations applied to a regular queue.
        I believe this is a very good compromise as it doesn't impose any mechanism by default, but if one wishes to, it allows the flexibility to name a temp queue just as you would name a regular queue.

        Show
        Rajith Attapattu added a comment - There was no consensus on a scheme to configure temp queues by default. However with the new addressing syntax it's now possible for a user to name a temp queue subject to the limitations applied to a regular queue. I believe this is a very good compromise as it doesn't impose any mechanism by default, but if one wishes to, it allows the flexibility to name a temp queue just as you would name a regular queue.

          People

          • Assignee:
            Rajith Attapattu
            Reporter:
            Rajith Attapattu
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development