Hiram Chirino wrote:
On 9/25/06, Gordon Sim <[EMAIL PROTECTED]> wrote:
When receiving an AMQP bind command asking that queue x be bound to
exchange y, how does combining these into a compound destination name of
some sort help us define a mapping for that command onto JMS semantics?
Doesn't that information uniquely identify the destination? If so,
then you can use jms semantics to send and receive messages from it.
I'm not with you I'm afraid.
On receiving the bind request I must ensure that any subsequent messages
published to exchange y (that match the given binding details) are
delivered to queue x.
A given JMS implementation can I'm sure find ways of doing that. My
point was that I don't think we can define a generic mapping for this
AMQP command onto JMS semantics.
