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...
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 What integration for it (if any), already exists "within" web2py for a "gevent'ed-deployment story" ? I don't know or care much for Tornado... From what I gather, it is similar to twisted in terms of asynchronous-coding requirements... 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? On Tue, Apr 9, 2013 at 2:53 PM, Niphlod <niph...@gmail.com> wrote: > > > On Tuesday, April 9, 2013 10:56:51 PM UTC+2, Arnon Marcus wrote: >> >> The first yield WILL block the thread, but as you say, only the thread of >> that connection. So the inter-thread communication would then be solved via >> another "shared" process - Redis - which will act as a message broker, >> listening to submissions and submit publications for subscribers. >> > > redis is not required either, but that's what happens, yes. > > >> >> > I guess I can live with that, for now, our user-base is small enough I >> think... >> Apache is doing the same, right? >> >> > depends on the implementation choosen but basically yes, you're holding > either a thread or a process for as long as the SSE connection is alive. > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "web2py-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/web2py/bpx7ZcL67Co/unsubscribe?hl=en. > To unsubscribe from this group and all its topics, send an email to > web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
