Mon Nov 22 16:23:32 CET 2010
Thanks for the zotonic tip, I'll have a look at that. I don't need a
full CMS, but it'll be useful to compare websockets implementations.
I'm currently using nginx in front of mochiweb for comet and static serving etc.
nginx is not suitable for websockets as mentioned.. HAProxy supposedly
is, but I'm probably just going to listen directly with mochiweb for
websockets on another IP using a subdomain. This should work fine,
since I can validate the origin and permit traffic from the main
domain to the subdomain.
I'll be listening on the https port for websockets using either an
iptables forwarding rule, or setcap on the vm as detailed here:
On 22 November 2010 14:47, Pablo Platt <> wrote:
> Are you using a proxy in front of mochiweb for your websockets
> or just port forwarding with iptables?
> nginx doesn't support http 1.1 so I think it's not suitable for websockets.
> From: Richard Jones <>
> Sent: Mon, November 22, 2010 3:45:08 PM
> Subject: [erlang-questions] Websockets
> Is anyone using websockets off an erlang backend in production?
> I couldn't find any complete implementations, so here's my patch to
> mochiweb to support websockets:
> I'm planning to start using it on irccloud.com in the next week or
> two, as an alternative to the awkward comet hack in use currently.
> I'll report back once it's had some production use. In the meantime,
> I'm curious if anyone else has a working implementation or is using
> websockets in anger.
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:
More information about the erlang-questions