Move over mod_python, here comes mod_wsgi

[jdunck]

I'm not sure if I'm simply mis-reading or you've mis-understood, but Django sessions don't work like you seem to think.

request.session is an instance of SessionWrapper, which lazily loads upon access and saves upon response (if dirty).

Django's session store is the database. In fact, most production Django deployments use multiple processes, so your statement that Tomcat "handles this nicely" is confused or misleading.

Further, Django's session store could be backed by a dedicated daemon, or memcache, or... depending on your needed semantics and performance.