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 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.
