Hi, I am the author of Concurrence (http://opensource.hyves.org/ concurrence), a framework for creating massively parallel network applications. The framework also includes a fast WSGIServer, so naturally I would like to (re)use Pylons to build web-applications on top of it...
However, the Concurrence framework is not based on threading for concurrency, but instead uses libevent + tasklets (trough stackless or greenlets). This allows you to write code in a familiar sequential 'blocking' style, but at the same time, IO is handled asynchronously behind the scenes... The problem with using Pylons as a web-framework on top of it comes from the fact that some parts of Pylons (beaker, routes) rely on the python threading libraries for things like locking and thread locals. Thus there is a hard coded assumption that pylons apps will always be deployed in a threading based WSGI Server. Instead of trying to monkey patch Pylons or the standard python threading libraries with my equivalents (TaskLocal), would it not be nice if the threading stuff could be factored out of Pylons and that it would be up to the 'container / WSGIServer' to provide these services trough some well defined API? Maybe this is something that should be handled at the WSGI level, but I would like to hear any thoughts on this from the Pylons devs... Cheers, Henk Punt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
