I'm didn't follow this discussion closed enough, probably what I have to say was already said, but ...
> So essentially, if you run web2py on-top of tornado's I/O-loop, you should > be able to use these YieldPoint classes within the controller-actions. I guess not, but I may be wrong. Using web2py served by tornado you need to use the tornado WSGIContainer that invalidates the async nature of tornado. Tornado is (at least was) not WSGI compliant to be able to be async. > The question that remains open to me is, can you do it even "without" > tornado's I/O-loop... (?) Yes, with Greenlets. Can be done today without any change to web2py internals or other WSGI framework. And probably is, currently, the only option for WSGI Applications. See bottle docs about it: http://bottlepy.org/docs/dev/async.html It's just a question how you implement and how you deploy. Ricardo -- --- 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.
