[
https://issues.apache.org/jira/browse/QPID-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1308.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.7
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.
> JMS Temprory Queue naming
> -------------------------
>
> Key: QPID-1308
> URL: https://issues.apache.org/jira/browse/QPID-1308
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
> Attachments: temp_queue_naming.patch
>
>
> 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"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
