Robert Godfrey wrote:
The exchange to which temporary queues are bound should already be
configurable... That I don't have a problem with.
Great, I didn't realise that! Is the binding key used also configurable?
If the routing details can be separately configured, the name of a
temporary queue is probably only interesting in the clues it gives as to
usage (e.g. making it easy to see that a queue that appears to be
growing rapidly is a temp queue used as part of 'app-a' by 'user-b'
_might_ be valuable).
Providing the scheme safely avoids name conflicts I don't see much
_danger_ in it being configurable, though it may well be possible to
have one scheme that conveys all the useful information would remove
much of the value of such an option.
I guess I could envisage a scheme whereby default 'policies' would be
applied to queues using rules with naming patterns, but equally a
configurable mechanism for constructing the queues could just as well
request that policy directly.
