Folks I am not suggesting we move to MQTT necessarily. However, if we want a simple protocol with easy native python support, its not bad. STOMP is also good. It is pretty limiting that MQTT doesn't support headers. My only comment was that we are not actually using headers properly here.
The refactoring of the topic hierarchy and schemas is a good thing to do, but it shouldn't be driven by the protocol. If we want to clean this up anyway, then I'm +1, but I don't consider it urgent. Paul PS MQTT does support reliable delivery. I don't understand the discussion that says it doesn't. On 4 September 2014 15:09, Imesh Gunaratne <im...@apache.org> wrote: > Based on the above discussion, I guess we need to change the the existing >> Stratos messaging model to support the Pub/Sub model and MQTT protocol. >> > > I think this statement is not correct, currently we use Pub/Sub model in > Stratos messaging system. > AFAIU we are looking at two concerns in this discussion: > > 1. Using hierarchical topics to avoid using headers. > 2. Moving to MQTT from AMQP > > Just to be clear, point 1 and point 2 are two different things, we might > not need to move to MQTT to support point 1. > > +1 for Paul's suggestions to look at MQTT. It seems to be a very light > weight messaging protocol compared to AMQP [1] however I can see following > limitations: > > 1. Unreliable (however can make use of TCP guaranteed delivery and > ordering) [1], [2] > 2. Less support for security (SSL can be used, has username/password > support in v3.1 [3]) > 3. No support for queues (by design, might not be a problem for us now) > > On high level, MQTT has been designed for resource-constrained devices and > low bandwidth, high latency networks. > > [1] > http://blogs.vmware.com/vfabric/2013/02/choosing-your-messaging-protocol-amqp-mqtt-or-stomp.html > [2] > http://stackoverflow.com/questions/10462297/mqtt-not-reliable-delivery-instead-of-tcp > [3] > http://mqtt.org/wiki/doku.php/questions?s[]=delivery#qdoes_mqtt_support_security > > Thanks > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
