On Wednesday, April 10, 2013 12:53:01 AM UTC+2, Arnon Marcus wrote: > > Well, again, Redis IS required for inter-controller communication... (the > notorious "green arrows" in my picture...) Which is, to me, a trivial > requirement for most production use-cases... >
I use redis too in standard deployments, it was only for next eyes coming to this thread. > > > So, to sum-up : > - For inter-controller communications, you need an external message-broker > (Redis/RabbitMQ). > - To avoid "polling" the message-broker, you need concurrency > (threads/processes/Eevntlets). > > Now we can move on to Socket.IO: > http://www.youtube.com/watch?v=TH-ZCuOdrQE > yeah! > > What integration for it (if any), already exists "within" web2py for a > "gevent'ed-deployment story" ? > Noone within web2py, but the library gevent-socketio is advertised as "simple to inject". > I don't know or care much for Tornado... From what I gather, it is similar > to twisted in terms of asynchronous-coding requirements... > well, tornado is a "friendlier" implementation of the twisted event-loop for webservers. Given though that the "partnership" between gevent and socketio is stronger, I'd go for gevent too. > The way I understand it, unless there is some special-integration code, > then using socket.io, would usually require running an independent > gEvent'ed Socket.IO server - and routing "/socket.io/*" URI's in the > web-server to it... It will then deal with all browser's "client-socket.io" > interactions, and inter-operate with web2py via a message-broker (as noted > above). > > Am I understanding this correcty? > yes. Also if it was a single process (i.e. you successfully embed gevent-socketio within web2py) with your requirements a message broker would be needed anyway: it's up to you if you want to have a single process serving "two masters" (standard traffic and socket-io ones) or two separate processes handling their own business. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
