Hi Bernat, I did some with MQTT in Java/Android and JavaScript with Paho, but never used it with Pharo nor in any of our products.
Regards! Esteban A. Maringolo 2015-04-08 10:55 GMT-03:00 Bernat Romagosa <tibabenfortlapala...@gmail.com>: > Hi Esteban, > > did you finally choose MQTT? I'm in the beginning of a project right now > where we need to communicate with a bunch of devices and we've considered > MQTT, but we don't know whether to use some existing broker like mosquitto > or implement it in Pharo. Have you been down this path? > > Thanks! > Bernat. > > 2014-11-24 11:55 GMT+01:00 Andres Fortier <andres.fort...@gmail.com>: >> >> Hi Stef, >> >> thanks! Glad to be doing things in Pharo :) >> >> On Sun, Nov 23, 2014 at 9:24 AM, stepharo <steph...@free.fr> wrote: >>> >>> Hello Andres >>> >>> nice to see you on this list :) >>> >>> Stef >>> >>> Le 19/11/14 19:40, Andres Fortier a écrit : >>> >>> Hi Esteban, >>> Never used either of them, but IIRC there was a Jabber package in >>> Visualworks (JabberXMPP?), although not sure if it provided both client and >>> server. There is also >>> http://www.squeaksource.com/@zQrCJXpxIQLxqde8/tV369AO0. Seems dated, but >>> maybe worth a shot considering you only need the server side? >>> >>> HTH, >>> Andrés >>> >>> On Wed, Nov 19, 2014 at 3:06 PM, Esteban A. Maringolo >>> <emaring...@gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> I'll be needing to add bidirectional messaging to our current Android >>>> (Java) application, and as usual I'm expecting to manage the server side of >>>> the communication with Pharo. >>>> >>>> I'm evaluating two alternatives, but I'm in open to other, proven, >>>> options. >>>> >>>> Option 1. WebSockets >>>> Open a WebSocket on each device, and push/retrieve messages from each of >>>> these, tracking the device id if I need to recreate a new socket (avoiding >>>> recreating new sockets in case of connectivity issues, very common). >>>> >>>> Option 2. MQTT [1] >>>> This is basically a mobile oriented MQ, super low footprint on mobile. >>>> For what I saw, I could implement the server using an intermediate MQ >>>> (RabbitMQ) and use STOMP to connect to it. >>>> >>>> Option 3. XMPP [3] >>>> Provides several features I'll need in the future, like file transfer in >>>> addition to regular text messaging. It is very well supported in Android >>>> with Smack [4], but I don't know if we have a Pharo server for it, or if >>>> somebody ever played with it. >>>> >>>> By means of simplicity and use load I favor option 1, because I can >>>> understand it better, and as everything moves towards web based >>>> technologies, I could implement WAMP [5] on top of that in the future. >>>> >>>> Right now I'd need to have a hundred websockets opened at the same time, >>>> which doesn't sound like a heavy load to me, but I certainly don't know. In >>>> the future it could be an order of magnitude bigger, and that's why I don't >>>> discard more complex solutions like XMPP or MQTT. >>>> >>>> Regards! >>>> >>>> >>>> [1] http://mqtt.org/ >>>> [2] https://github.com/svenvc/docs/blob/master/neo/stamp.md >>>> [3] http://xmpp.org/ >>>> [4] http://www.igniterealtime.org/projects/smack/ >>>> [5] http://wamp.ws/ >>>> >>>> >>> >>> >> > > > > -- > Bernat Romagosa.
