At 10:59 26/03/99 , Oleg Broytmann wrote:
Hello.
Continuing the subject... Next question. If Zope opens one connection to a database, how does Zope manage concurrency? Currently, when two CGIs run in parallel, every CGI opens its own connection to the database, lock neccessary tables, and Postgres manage concurrency very good (even detecting deadlocks). Next Postgres version (6,5) will have Multi-version Concurrency Control. But all this is for different sessions. Zope opens only one session. Is it a problem with concurrency?
Zope manages concurrency by being single-threaded... so only one query at a time, on ANY connection... -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-6254545 Fax: +31-35-6254555 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------