Thanks! I guess I'll use mosquitto as a middleware then, and
Zinc/Websockets from Pharo.
Best,
Bernat.
2015-04-08 16:47 GMT+02:00 Esteban A. Maringolo :
> 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.
>
>
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 :
> Hi Esteban,
>
> did you finally choose MQTT? I'm in the beginning of a project right no
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!
Hi Stef,
thanks! Glad to be doing things in Pharo :)
On Sun, Nov 23, 2014 at 9:24 AM, stepharo 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
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.squeaksour
I've used XMPP extensively for several projects, from python, JavaScript,
and Squeak - the wonderful thing about it is that you can start off simple
using just chat messages, but then add more features like pub sub,
conference rooms, service discovery, etc. Scalability is built into the
system, and
> On 19 Nov 2014, at 20:52, Esteban A. Maringolo wrote:
>
> My current use case is pretty simple, being able to push requests to the
> remote devices, and gather the data back, assuming the remote devices
> (clients) are already connected to the server, which is a client-related
> problem wit
My current use case is pretty simple, being able to push requests to the
remote devices, and gather the data back, assuming the remote devices
(clients) are already connected to the server, which is a client-related
problem with any messaging solution.
I learn about MQTT when looking for alternati
Hey Esteban,
Since you seem to need to scale to 1000s of concurrent connections, I would go
for option 2. RabbitMQ will then work as a demultiplexer and you gain options
for using more than one Pharo worker for processing traffic, if that ever
becomes necessary.
BTW, I never heard of MQTT and
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 s
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
11 matches
Mail list logo
