You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/02/15 12:54:06 UTC
[jira] Created: (QPID-371) Client and Broker do not validate
(routing key) topic name
Client and Broker do not validate (routing key) topic name
----------------------------------------------------------
Key: QPID-371
URL: https://issues.apache.org/jira/browse/QPID-371
Project: Qpid
Issue Type: Bug
Components: Java Broker, Java Client
Reporter: Martin Ritchie
>From the AMQP spec:
The routing key used for a topic exchange MUST consist of words delimited by dots. Each word may contain the letters A-Z and a-z and digits 0-9.
The routing pattern follows the same rules as the routing key with the addition that * matches a single word, and # matches zero or more words. Thus the routing pattern *.stock.# matches the routing keys usd.stock and eur.stock.db but not stock.nasdaq.
One suggested design for the topic exchange is to hold the set of all known routing keys, and update this when publishers use new routing keys. It is possible to determine all bindings for a given routing key, and so to rapidly find the message queues for a message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-371) Client and Broker do not validate
(routing key) topic name
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-371:
--------------------------------
Fix Version/s: M3
> Client and Broker do not validate (routing key) topic name
> ----------------------------------------------------------
>
> Key: QPID-371
> URL: https://issues.apache.org/jira/browse/QPID-371
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Reporter: Martin Ritchie
> Fix For: M3
>
>
> From the AMQP spec:
> The routing key used for a topic exchange MUST consist of words delimited by dots. Each word may contain the letters A-Z and a-z and digits 0-9.
> The routing pattern follows the same rules as the routing key with the addition that * matches a single word, and # matches zero or more words. Thus the routing pattern *.stock.# matches the routing keys usd.stock and eur.stock.db but not stock.nasdaq.
> One suggested design for the topic exchange is to hold the set of all known routing keys, and update this when publishers use new routing keys. It is possible to determine all bindings for a given routing key, and so to rapidly find the message queues for a message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-371) Client and Broker do not validate
(routing key) topic name
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473359 ]
Martin Ritchie commented on QPID-371:
-------------------------------------
For the broker this should be addressed in QPID-3
> Client and Broker do not validate (routing key) topic name
> ----------------------------------------------------------
>
> Key: QPID-371
> URL: https://issues.apache.org/jira/browse/QPID-371
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Reporter: Martin Ritchie
>
> From the AMQP spec:
> The routing key used for a topic exchange MUST consist of words delimited by dots. Each word may contain the letters A-Z and a-z and digits 0-9.
> The routing pattern follows the same rules as the routing key with the addition that * matches a single word, and # matches zero or more words. Thus the routing pattern *.stock.# matches the routing keys usd.stock and eur.stock.db but not stock.nasdaq.
> One suggested design for the topic exchange is to hold the set of all known routing keys, and update this when publishers use new routing keys. It is possible to determine all bindings for a given routing key, and so to rapidly find the message queues for a message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (QPID-371) Client and Broker do not validate
(routing key) topic name
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner closed QPID-371.
------------------------------
Resolution: Won't Fix
0-10 has more relaxed naming rules
> Client and Broker do not validate (routing key) topic name
> ----------------------------------------------------------
>
> Key: QPID-371
> URL: https://issues.apache.org/jira/browse/QPID-371
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Reporter: Martin Ritchie
> Fix For: M3
>
>
> From the AMQP spec:
> The routing key used for a topic exchange MUST consist of words delimited by dots. Each word may contain the letters A-Z and a-z and digits 0-9.
> The routing pattern follows the same rules as the routing key with the addition that * matches a single word, and # matches zero or more words. Thus the routing pattern *.stock.# matches the routing keys usd.stock and eur.stock.db but not stock.nasdaq.
> One suggested design for the topic exchange is to hold the set of all known routing keys, and update this when publishers use new routing keys. It is possible to determine all bindings for a given routing key, and so to rapidly find the message queues for a message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.