Robert Godfrey wrote:
To shed some light on the use of the custom property...
It is used to support the notion of getJMSDestination() on a JMSMessage
That is JMS requires us to know the original destination (in JMS terms)
that
the message was sent to, We originally did this by sending the BindingURL
as a long string, however this proved to be very inefficient.
The current solution of sending a byte-encoded representation of the
Destination is still not correct. In general we need to think through the
whole notion of what a destination is in QPID / AMQP.
We probably need a change at the protocol level to ensure that the original
intended destination is included in the header, but for this we need to be
clear on what a destination is. It cannot simply be exchange and routing
key, as we need to consider the case of topologies of brokers wired
together. Thus we need a globally unique destination name to provide
correct equality semantics.
- Rob
Thanks for the update Rob. Was I wrong in saying that property is only
ever read when the session is in client acknowledge mode? Or is that
just a bug?
