Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC

Back to discussions
Expand all | Collapse all

Queue/Topic addressing - (was: RE: [amqp-bindmap] Groups - OASIS AMQP Bindings & Mapping Technical Committee 20150113.pdf uploaded

  • 1.  Queue/Topic addressing - (was: RE: [amqp-bindmap] Groups - OASIS AMQP Bindings & Mapping Technical Committee 20150113.pdf uploaded

    Posted 01-13-2015 18:26
    Thanks Steve.   Robbie- on this from the minute on JMS:   Robbie initiated email discussions on OASIS and Qpid mailing lists re the queue/topic name issues discussed at the previous TC meeting. Result is that no address-related naming conventions will be defined. Both AMQP and JMS will treat the names as opaque addresses. Rob Godfrey indicated that there will at some point be a need to define how to map queues/topics to AMQP addresses apart from more specific configuration parameters. It is a requirement to be able to access all AMQP functionality from JMS without extensions. -           I must have missed this but could you forward a pointer to the thread where this was decided?  Last I saw on the OASIS list is that while there were differing views, there was support for defining this. -           @Rob G & Robbie- if we don’t define the wireline of topics/queues/subscriptions (with levels, wildcards, etc) here, then will this go into the addressing doc or how will this be handled?    I am hoping we can get to the point where, like MQTT, there is a specification for the syntax and semantics of these – otherwise it will be difficult if not impossible to achieve the objective of various/all runtimes embedding client APIs  “out of the box” that just work with 3 rd party brokers….  MQTT defined this, why can’t AMQP?   Thanks Shawn   From: amqp-bindmap@lists.oasis-open.org [mailto:amqp-bindmap@lists.oasis-open.org] On Behalf Of Steve Huston Sent: January-13-15 11:50 AM To: amqp-bindmap@lists.oasis-open.org Subject: [amqp-bindmap] Groups - OASIS AMQP Bindings & Mapping Technical Committee 20150113.pdf uploaded   Submitter's message Added Mark Blair's attendance. -- Mr. Steve Huston Document Name : OASIS AMQP Bindings & Mapping Technical Committee 20150113.pdf No description provided. Download Latest Revision Public Download Link Submitter : Mr. Steve Huston Group : OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC Folder : Meeting Notes Date submitted : 2015-01-13 08:50:08 Revision : 1  


  • 2.  Re: [amqp-bindmap] Queue/Topic addressing - (was: RE: [amqp-bindmap] Groups - OASIS AMQP Bindings & Mapping Technical Committee 20150113.pdf uploaded

    Posted 01-15-2015 10:11
    Hi Shawn, I don't believe there has been anything further on the subject since the last few mails I sent on the original thread mid-December. I was conveying where I believed the conversation got to before it faded, and my current view on what the JMS mapping would or rather would not do in this area. Rob clarified that regardless of the actual addresses used, we would likely want to define some way to pass additional options through the vendor-specific String parameter for session.createQueue(...) / session.createTopic(...) calls, such that they could be used to configure certain things such as source/target options to access certain AMQP functionality. As I think I mentioned in those earlier mails, I would see the Addressing spec as the way to go in terms of utilising global addresses to improve cross-vendor naming interoperability. I also seem to recall the last published draft of the Addressing spec I read as having some sort form of address pattern matching noted in it, but I admit it has been some time since I looked at it so I am not sure on the current state. Certainly, I think any work on the matter needs to happen via the core AMQP TC rather than 'just' a particular mapping. Robbie
    Original Message


Related Content