[Web-SIG] websocket support in WSGI
sh at defuze.org
Tue May 22 09:38:18 CEST 2012
> In other words: The responsibility for the connection (and socket) is
> passed to the application.
> This works well with traditional threaded servers. The application can
> spawn a new worker thread, put the job into a queue or whatever and then
> return from the application callable, allowing the server thread to
> continue handling new connections.
This is exactly how ws4py was implemented when using CherryPy for the HTTP
server performing the handshake . There's also a WSGI middleware  but
it's heavily geared towards gevent and may not be reusable easily elsewhere
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Web-SIG