Paul Rubin <http://[EMAIL PROTECTED]> writes: > If the transactions are simple and low-latency, then it can be enough > to have a single process own the whole database, and have every client > send all its requests to the db process.
Meant to say: it can be enough to let the clients lock the database, do their thing quickly, and release the lock. What I described is of course how it's usually done with SQL. Sigh. Other approaches include running the whole app in one process (asyncore/twisted), having a multi-threaded app where one thread owns the db and serializes requests through Queues, etc. -- http://mail.python.org/mailman/listinfo/python-list
