You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2008/10/01 21:35:44 UTC
[jira] Created: (QPID-1308) JMS Temprory Queue naming
JMS Temprory Queue naming
-------------------------
Key: QPID-1308
URL: https://issues.apache.org/jira/browse/QPID-1308
Project: Qpid
Issue Type: Improvement
Components: Java Client
Affects Versions: M4
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: M4
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.
[jira] Updated: (QPID-1308) JMS Temprory Queue naming
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-1308:
-----------------------------------
Attachment: temp_queue_naming.patch
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.
> JMS Temprory Queue naming
> -------------------------
>
> Key: QPID-1308
> URL: https://issues.apache.org/jira/browse/QPID-1308
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M4
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: M4
>
> 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.
[jira] Updated: (QPID-1308) JMS Temprory Queue naming
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-1308:
-----------------------------------
Affects Version/s: (was: M4)
> 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
> 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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1308) JMS Temprory Queue naming
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-1308:
------------------------------
Fix Version/s: (was: M4)
This patch has not been applied and thus is not part of M4. We should revisit this topic at a later date.
> JMS Temprory Queue naming
> -------------------------
>
> Key: QPID-1308
> URL: https://issues.apache.org/jira/browse/QPID-1308
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M4
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> 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.