1. How? Usually by a yield somewhere. Where? The already existing open connection knows where. 2. Slow down there, you're overthinking it. Web2py comes with this.
Look at web2py/gluon*/contrib/*comet_messaging.py And... watch this video by Bruno Rocha http://vimeo.com/18399381 On Thursday, April 4, 2013 5:29:56 PM UTC-7, Arnon Marcus wrote: > > The only thread on this in this group has been deleted. > > I have a few questions: > > 1. The way I understand this, an implementation would be via a > controller-action that receives the event-stream-request, then responds > with a "200 OK" and that MIME thing, to affirm the connection. But from > that point onward, new responses should be sent over the same open > connection. How is the response-object being generated and sent without a > request? How does it know where to send it to? > > 2. I would like to make a shared-collaborative view for multiple users, > that any changed done by one, is reflected automatically in all the others. > How would I go about doing that? Since web2py executes on each request, I > would have to hold connection-data of all open-connections, in some > semi-persistent location - would I have to use some > external/internal caching? Is there some automatic session-saving already > built-in web2py that can be useful? > -- --- 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.
