Rob,
agree - that is better than my first wing at it, let's see if we have
more comments, and then raise a JIRA for it
Carl.
Robert Godfrey wrote:
Hi Carl,
I think the general idea is good...
I would suggest a slight refinement in that generally the binding key
is the most useful part of the "topic".. so I would suggest a queue
name something like
<binding-key>@<exchange-name>_<uuid>
where
<uuid> is a 36 character UUID string produced (for example) by
java.util.randomUUID().toString()
<binding-key> is a maximum of 207 single-byte characters from the
binding key used.
<exchange-name> is as many characters as possible from the name of the
exchange while still fitting into a 255 character queue-name.
this would give queue names like
[EMAIL PROTECTED]
Thoughts?
Rob
On 19/03/2008, Carl Trieloff <[EMAIL PROTECTED]> wrote:
I would like to propose the following or a variation of the following.
Please chime in.
Issue, when we setup JMS topics is that it creates a tmp queue for each
connection with an ugly name. This
makes it hard for admins to map the temp queues to the topics.
I would like to suggest that we adopt a naming convention across Qpid to
solve this issue. Here is my first
suggestion.
For temp queues created by JMS clients that the temp queue name contains
up to 128 bytes from the exchange
name 'topic' and then the last 128 bytes be a magic to make the queue
name unique.
Another options would be:
up to first 128 bytes from exchange name, up 64 bytes from connection
id, and 64 bytes of magic.
This would only apply to temp queues created by the JMS clients.
thoughts / comments please
Carl.
