Hello everyone,

we here at DESY are using pound for quite a long time now between
caching Apache and a buttload of Zope servers. It run's extremely well,
thanks for that great piece of software!

What it already does is being persistent on cookie based sessions, works
like a charm.
Now we want users with specific URL patterns and no cookie to be
redirected to another pool of Zope-Servers. There they get a session
cookie and should be held on that server.

Requester 1 (no cookie) http://mysite.desy.de/content/ ->
one of pool A
-> sets cookie
Requester 1 (session cookie) http://mysite.desy.de/content/ ->
same of
pool A

Requester 2 (no cookie) http://mysite.desy.de/manage/ ->
one of pool B
-> sets cookie
Requester 2 (session cookie) http://mysite.desy.de/manage/ ->
same of
pool B
Requester 2 (session cookie) http://mysite.desy.de/DIFFERENT/
-> same of
pool B

Notice that requester 2 with cookie and a URL that doesn't contain the
keyword /manage should be held on the same backend of pool B.

I am trying to wrap my head around this for quite a few days (on and
off) now. I've read docu, manpage and searched two years of the mailing
list...

Does anyone know if this is doable or not? If this is doable, a short
hint how?

Thanks in advance! /Carsten

------------------------------------------------------------------------
Carsten Germer         Deutsches Elektronen Synchrotron (Web-Office, IT)
phone:  +49-40-8998-1661                                    Notkestr. 85
web: http://wof.desy.de                       
            22607 Hamburg
e-mail: carsten.germer(at)desy.de                                   Germany
------------------------------------------------------------------------

Hi Carsten,

We host a lot of Zope/Plone systems and what we have tended to do where
we have a pool of Zope systems serving the same web application is to
use a shared session backend. 
You can mount, say, a /session folder in each of the Zope applications
from a central ZEO server and have the session information stored that
way instead of using the in-memory /temp_folder storage mechanism.

It works pretty well - though I don't know what your session read/write
ratios are like - ours are mostly one time writes and then the remainder
are mainly state information when requests are passed between the many
app servers (one of our bigger systems runs over [at the last count] 10
physical servers), so YMMV if you do a lot of session writes.

Regards

-John

 John Snowdon - IT Support Specialist
-==========================================-
 School of Medical Education Development 
 Faculty of Medical Sciences Computing
 University of Newcastle

 Email : j.p.snowdon(at)ncl.ac.uk

[...]