Re: Server-side Websocket implementations in non-event driven HTTP Server Environments

I think Mojolicious has a forking Websocket implementation in Mojo::Server::Daemon.

Personally, I like in-process Websockets, as I use them to communicate between clients. Usually I don't have an elaborate message queue schema set up, so distributing information is done easiest by keeping all clients connected to the same process. This is where AnyEvent comes in very handy for me.

Comment on Re: Server-side Websocket implementations in non-event driven HTTP Server Environments

Replies are listed 'Best First'.
Re^2: Server-side Websocket implementations in non-event driven HTTP Server Environments by unlinker (Monk) on Jun 09, 2013 at 02:44 UTC
Thanks for responding. Could you explain "in-process websockets" please? Do you mean: there is a single process (same pid) that handles communication with all the connected clients? The documentation for Mojo::Server::Daemon lists it as a non-blocking server and has an event loop. How is that different from Twiggy and other event driven HTTP servers?	[reply]
Re^3: Server-side Websocket implementations in non-event driven HTTP Server Environments by Corion (Patriarch) on Jun 09, 2013 at 06:57 UTC
Yes, that's what I meant by "in-process websockets". And it seems I misread Mojo::Server::Daemon then - it seems no different from Twiggy.	[reply]