Hi, If you are doing serious amount of (idle) websocket connections you should consider uWSGI "offloading" websocket event loop to an async offload thread:
http://uwsgi-docs.readthedocs.io/en/latest/articles/OffloadingWebsocketsAndSSE.html http://uwsgi-docs.readthedocs.io/en/latest/OffloadSubsystem.html This way you can handle heavy concurrency better. If you are not worried about scalability, don't worry about offloading, as it will add an extra complexity layer to your development. Thanks, Mikko On 9 January 2017 at 10:39, Avraham Serour <[email protected]> wrote: > Hi, > > I'm making a python websocket server application, I took a look at the > example and already have a proof of concept running. > > If I understand correctly each worker holds one websocket, so how to send > a message from one worker to another? Is that possible? > > I'm currently using redis as a backend, so one worker receives the message > from redis and then it would need to redirect to the correct socket back to > the client. > > Any thoughts? > > Avraham > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > -- Mikko Ohtamaa http://opensourcehacker.com http://twitter.com/moo9000
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
