Hiram Chirino wrote:
So basically if the destination contained all of the binding
information. The producers would be able to create the correct bind
request. So that messages are delivered to the right queues.
And since that binding information specifies queues where messages are
being delivered, I think the consumer side of things should have
enough information to create it's subscription.
Ok, I think we got our wires crossed. Yes, I agree that it is relatively
straightforward to map from JMS semantics onto AMQP commands.
It is the reverse mapping that I was commenting on (i.e. responding to
the bind request, not issuing it).
