On Tue, Dec 15, 2009 at 2:39 PM, Joan Miller <pelok...@gmail.com> wrote: > Pylons is a great project, thanks! But I'm supposed that it would be > faster if it were ready for concurrency. > > Today is not necessary to use Twisted; it's great, but forces you into > callback hell. In change, pyev [1] is a great solution. > > [1] http://code.google.com/p/pyev/
Pylons itself does not deal with network I/O or threads; it just takes a WSGI request and returns a WSGI response. What you'd need is a WSGI server that uses pyev. I don't know if there are any. But if you do find one that has Paste-compatible entry points, you can configure it in the server section of the INI file. The flup project (http://trac.saddi.com/flup) has several servers, but none that use pyev as far as I can tell. Pylons does not make any attempt to avoid blocking. However, most blocking occurs with network or database access. The network part is handled by the WSGI server. Pylons does not include a database (just a suggested configuration for SQLAlchemy), so you're on your own there. I'm not sure if disk access is considered blocking, but if so, the session configuration and Mako template caching would be concerns. -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@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.
