Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

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

by unlinker (Monk)
on Jun 09, 2013 at 02:44 UTC ( #1037898=note: print w/ replies, xml ) Need Help??


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
Re^3: Server-side Websocket implementations in non-event driven HTTP Server Environments
by Corion (Pope) 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.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1037898]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (5)
As of 2014-12-20 20:46 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (98 votes), past polls