Hi Gordon, Thanks for adding this. It should be definitely good for interoperability.
Thanks & Regards Jakub On Mon, Aug 31, 2015 at 11:30 AM, Gordon Sim <[email protected]> wrote: > On 08/14/2015 05:17 PM, Jakub Scholz wrote: > >> The compatibility issue across different brokers is for sure unfortunate. >> Although it at least has a workaround. I wonder how the other brokers plan >> to deal with the non-JMS clients. It would sound a bit strange if you tell >> someone to use a filter "JMSCorrelationID = 123" in a C++ AMQP client. >> >> The "C++ broker" toggle is an interesting idea - it would probably make >> the >> switch to other brokers easier. On the other hand, it sounds like a bad >> marketing - it would be hard to convince people about the benefits of AMQP >> if you then tell them that they have to use this and that switch for >> compatibility between different AMQP components :-o. >> > > Just fyi, the c++ broker now recognises JMSCorrelationID and the other JMS > header names in addition to the 'amqp.' equivalents[1]. Hopefully that > improves interoperability a bit in the short term while we await a spec > that everyone can implement. > > [1] https://issues.apache.org/jira/browse/QPID-6714 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
