This is cross-posted from Pylons-discuss, where it's not getting much attention. It's a bit off-topic, but does touch on SA + heavy threading.
Any feedback welcome
------------------
We've got a commercial project we're developing that currently uses
Twisted + SQLAlchemy that we're thinking of moving to Pylons +
SQLAlchemy. The UI of the program is very AJAX-heavy, and consists of
many small requests that each hit the database, then return JSON
formatted data to the front-end.
Twisted has worked pretty well under load with this scheme, but its
twisted.web interface is clumsy to use; it works, but we're looking for
something with a bit better support for sessions and URL resolving (and
templating is a nice bonus). We've been waiting forever and ever for
twisted.web2 to arrive, and we need to move forward now. Hence the
interest in Pylons.
But I've read story after story about the evils of thread-based systems
failing in strange ways under load. I think I understand that
best-practices for for threaded Paste apps is to leave the global
namespace alone, and start and complete a single request in a single
thread -- "finish what you start". Is that really sufficient for
creating reliable multi-threaded apps under load? Or is there perhaps
some other concurrency mechanism that will work with SA that we've
missed?
Rick
