you can do it with web2py right now without any change. You just need to code your own zmq hooks.
As you stated earlier, until something gets packed into stable python, there's no way around GIL. tl;dr; anyone wanting to run python in an evented loop needs to go around GIL and choose its own implementation (gevent, eventlet, pulsar, twisted, etc). If you need an evented loop, run web2py on it with anyserver.py, it will be alive and kicking as it is right now. The missing part is messaging, and there are several stable modules/techs/external something that you can leverage from and that web2py can definitely not track (hence the previous recommendation to pack them as plugin, if you wish) until they get somewhat standardized inside python itself. On Tuesday, April 16, 2013 10:52:07 PM UTC+2, Arnon Marcus wrote: > > This way, it could be future-proofed. As web2py looms, and 2014 arrives, > you could only need to modify the internals of this integration, to support > PEP380 (Python 3.3's "yield from") and/or the higher-level Tulip > implementation (Python 3.4) - All without breaking existing code - The > controller-actions would still use the same decorators-syntax - it's just > their back-room implementation that would be different. > > Here is what is being done today that can be implemented, even for web2py > 2.x: > http://www.youtube.com/watch?v=again with gevent+zmq. > wLLHv5GbZiQ<http://www.youtube.com/watch?v=wLLHv5GbZiQ> > -- --- 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.
