[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [amqp-bindmap] Groups - OASIS AMQP Bindings & Mapping Technical Committee 20150127.pdf uploaded
|
Hi Steve, Thanks for this.
I’d like to suggest a rewording of the goal I stated relative to the JMS Mappings document and addressing discussion to be as clear as possible (admitting that
someone else could perhaps make it even clearer). Where the minutes state in “Progress on JMS” An important goal raised by Shawn McAllister is the ability for an MQTT endpoint
using JMS to be able to subscribe to filters/topics served by AMQP. I’d suggest changing to: An important goal raised by Shawn McAllister is the ability for an MQTT endpoint to communicate over MQTT to a message broker which is then connected via AMQP to an application using a JMS API. In this situation, the topic
and topic filters (ie. Subscriptions) supported by MQTT need to be interoperable (imo without mapping or conversion complexity) with the capabilities offered to the application which is using a JMS API with an AMQP wireline. In pictures: Application A
ß----- MQTT wireline --à
message broker ß--AMQP wireline --à
JMS API ß------à
JMS application Where the topic syntax over the MQTT connection is supported on the AMQP connection. Similarly, the JMS client should be able to issue subscriptions with the
same wildcarding capabilities as the MQTT client. If we want AMQP to be richer from a subscription capability pov then ok with me – but as a minimum, be able to do what MQTT can do. Thanks Shawn
From: amqp-bindmap@lists.oasis-open.org [mailto:amqp-bindmap@lists.oasis-open.org]
On Behalf Of Steve Huston Submitter's message
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]