Python3 on the Web

Paul Rubin http
Sun Mar 8 04:05:39 CET 2009

Tim Roberts <timr at> writes:
> At that level of load, CGI is perfectly workable, and it's certainly the
> easiest of the choices for development and exploration.

One problem of CGI even at very low loads is that it's harder to
handle the case where two hits arrive at the same time and want to
save data.  You either have to mess around with file locking and
waiting, or use an external database that handles concurrency
(normally this means you end up with a persistent process anyway), or
some other kludge.  With a persistent server you can use
SocketServer.ThreadingServer and ordinary python queues to communicate
with a single thread that's in charge of the persistent data.

More information about the Python-list mailing list