So this means the websocket runs in its own Greenlet and I ask it if it has produced result and if not I check redis for messages.
>From your text I assume the websocket Greenlet is exposed through >uwsgi.connection_fd(). Can I do all the normal Greenlet magic on the exposed Greenlet for the connection? Thanks ----- Reply message ----- From: "Roberto De Ioris" <[email protected]> To: "uWSGI developers and users list" <[email protected]> Subject: [uWSGI] Python Decorators Date: Thu, May 16, 2013 23:09 > Sorry that was just me messing up. > > I still would like to know how I can work around the fact that I cannot > call the uwsgi api from with a Greenlet. > Any tips would be greatly appreciated. Some of the api calls requires to be called from the greenlet mapped to the request (like websockets one). The trick with websockets is waiting for both uwsgi.connection_fd() and redis fd. If uwsgi.connection_fd() is ready, you call the websocket_recv() otherwise you call redis (and so on) > > Cheers. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Alexandro G.S. Mancusi > Sent: 16 May 2013 19:54 > To: [email protected] > Subject: [uWSGI] Python Decorators > > Am I mistaken or are python decorators (uwsgidecorators) not available in > uwsgi 1.9.10? > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
