[erlang-questions] mochiweb vs. cowboy for websocket serevr

[Bob Ippolito]

After looking a bit more closely at this code (to write tests for and fix
an issue) I would not recommend using mochiweb's implementation of
websocket at this time. It's a contributed feature without many tests and
it does not appear to implement the full RFC spec. I can also see some edge
cases where incoming data might be lost (when websocket frames are
fragmented across http packets). The only really good reason to use this
implementation is if you really like mochiweb (perhaps for legacy reasons)
*and* you are willing to fix this code if it's broken for your use case.

On Sun, Jan 11, 2015 at 1:41 PM, Bob Ippolito <bob@REDACTED> wrote:

> I've used cowboy for most of the websocket stuff I've done in Erlang. The
> websocket support in mochiweb is newer and less mature. I haven't done any
> benchmarks on it.
>
> On Sun, Jan 11, 2015 at 12:24 PM, Akash Chowdhury <achowdhury918@REDACTED
> > wrote:
>
>> All,
>> I have to implement an websocket server in Erlang for video streaming.
>> (An Android client will send continous snapshot to Erlang server and Erlang
>> Server will send it to an User Interface which is developed in HTML5).
>> For this Erlang server, what will be better? Mochiweb, cowboy or
>> something different? What will scale better? Can someone please through
>> some light on it?
>> Any help will be highly appreciated.
>> Thanks.
>> -
>> Akash
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150111/a15b4549/attachment.htm>