<div style="white-space:pre-wrap">or vernemq with the websocket using mqtt js. you can even use ejabberd/mongooseim with the xmpp websocket client if you need messaging :)<br><br>Another solution would be using n2o or nitrogen. now you have a lot of choices ;)</div><br><div class="gmail_quote"><div dir="ltr">On Fri, 29 Jan 2016 at 17:09, Loïc Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">To add to that:<br>
<br>
If you need messaging or can design your application this way, then<br>
RabbitMQ is definitely a great solution.<br>
<br>
A few notes however:<br>
<br>
The SockJS in the Web STOMP plugin only accepts UTF-8 messages (this is<br>
also true of Bullet and most solutions that provide fallbacks). If you<br>
need binary, the Web STOMP plugin has a plain Websocket endpoint but<br>
that one has no fallback.<br>
<br>
The Web MQTT plugin currently does not work against the most recent<br>
RabbitMQ version, it will work against 3.6.1 onward. Right now you need<br>
to have an unreleased version of the RabbitMQ MQTT plugin that contains<br>
the required changes.<br>
<br>
The Web MQTT plugin is currently considered experimental. Feedback would<br>
however be much appreciated.<br>
<br>
Disclaimer: I wrote the Web MQTT plugin and am the current maintainer of<br>
the Web STOMP plugin.<br>
<br>
On 01/29/2016 04:57 PM, Santiago Fernández wrote:<br>
> If you want to take advantage from another Erlang system for your<br>
> development, take a look to RabbitMQ. There is a Web STOMP plugin (using<br>
> SockJS or plain WebSockets). I'm not sure what are the pros and cons of<br>
> STOMP vs plain WebSocket (bandwith, performance, scalability, etc) but<br>
> it is easy to integrate.<br>
><br>
> You can develop your own Erlang application an deploy it with the broker<br>
> in the same cluster, to avoid AMQP overhead (direct connection). Or you<br>
> can develop your own plugin using Erlang and using all RabbitMQ<br>
> infrastructure.<br>
><br>
> There is also a plugin for MQTT over WebSockets under development.<br>
><br>
> sorry for my english!<br>
><br>
><br>
><br>
> --<br>
> Santiago<br>
><br>
> On Fri, Jan 29, 2016 at 12:19 PM, Loïc Hoguin <<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a><br>
> <mailto:<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a>>> wrote:<br>
><br>
> On 01/28/2016 03:08 PM, Fred Hebert wrote:<br>
><br>
> I would be interested to hear any experiences you might have<br>
> in this<br>
> domain, and any recommendations you might have for erlang<br>
> libraries,<br>
> servers, etc. Has anyone done this? What stack did you<br>
> deploy? What<br>
> were the issues you encountered?<br>
><br>
><br>
> Sadly I'm afraid I can't be of much more help there. I've left a<br>
> lot of<br>
> my web dev work behind me. Something equivalent in spirit to the<br>
> <a href="http://socket.io" rel="noreferrer" target="_blank">socket.io</a> <<a href="http://socket.io" rel="noreferrer" target="_blank">http://socket.io</a>> of old, but with the Erlang frame<br>
> of mind is 'bullet',<br>
> developped to work with cowboy: <a href="https://github.com/ninenines/bullet" rel="noreferrer" target="_blank">https://github.com/ninenines/bullet</a><br>
><br>
> It's what I would consider your best bet, but I'm out of the<br>
> game when<br>
> it comes to that stuff and don't know what else may exist.<br>
><br>
><br>
> My recommendation today is to go with Websocket directly.<br>
><br>
> If you take a look at <a href="http://caniuse.com/#feat=websockets" rel="noreferrer" target="_blank">http://caniuse.com/#feat=websockets</a> you can<br>
> see that it will just work on close to 90% of the global market<br>
> share. Chances are your local market share is higher than that, but<br>
> it could also be lower (in particular if you are writing an<br>
> enterprise system).<br>
><br>
> Depending on when you will ship, it might not even make sense to ask<br>
> yourself this question anymore. If you ship even in 1 year it<br>
> already makes little sense, it's much easier to partially disable<br>
> functionality with a message recommending people update or switch<br>
> browser.<br>
><br>
> Note that in those %s, nearly 5% are about Opera Mini. Opera Mini is<br>
> a very particular browser that supports very little interactive<br>
> features. I would not count it in market share and so the total of<br>
> browsers that do support Websocket today is closer to 95%. If you<br>
> need to support Opera Mini, I don't think even something like Bullet<br>
> or Sockjs or other will work.<br>
><br>
> As far as which Websocket implementation to use, I would suggest<br>
> Cowboy of course, since I wrote it, but I will go as far as to<br>
> suggest Cowboy master if you care about Websocket compression,<br>
> although master is about to receive more breaking changes from the<br>
> work toward 2.0.<br>
><br>
> Cheers,<br>
><br>
> --<br>
> Loïc Hoguin<br>
> <a href="http://ninenines.eu" rel="noreferrer" target="_blank">http://ninenines.eu</a><br>
> Author of The Erlanger Playbook,<br>
> A book about software development using Erlang<br>
><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a>><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
><br>
><br>
<br>
--<br>
Loïc Hoguin<br>
<a href="http://ninenines.eu" rel="noreferrer" target="_blank">http://ninenines.eu</a><br>
Author of The Erlanger Playbook,<br>
A book about software development using Erlang<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div>