best way to serve wsgi with multiple processes

[Robin]

On Feb 11, 1:28 pm, Robin <robi... at gmail.com> wrote:
> On Feb 11, 12:10 pm, Robin Becker <ro... at reportlab.com> wrote:
>
> > We've used forked fastcgi (flup) with success as that decouples the wsgi process
> > (in our case django) from the main server (in our case apache). Our reasons for
> > doing that were to allow the backend to use modern pythons without having to
> > upgrade the server (which is required if using say mod_python). The wsgi process
> > runs as an ordinary user which eases some tasks.

I'm sorry - I originally missed the worked 'forked' and hence the
whole point of your message I think.

I looked at flup before but had forgotten about the forked version.
Having revisited it I think the forked version does keep a process
pool so each request is processed by a seperate process, which is
exactly what I wanted.

Cheers

Robin