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

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

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?

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

Replies are listed 'Best First'.
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]

In Section Seekers of Perl Wisdom