> Evil Son wrote
> > I must admit though that this behaviour is surprising since part of
> > the reason for fastcgi (as I understood it anyway) was to maintain
> > state/resources across requests - e.g. an open database connection.
> > It seems that PHP in fastcgi mode doesn't ... and I'm quite happy with
> > that as it avoids a whole class of bugs.
>
> > Thanks!

Jerry Stuckle:
> Not at all. Fastcgi just keeps the module in memory so it doesn't have
> to be loaded and initialized every time.
>
> Think about it - what happens if the last time the particular script was
> called it was a different user? You wouldn't want someone else to get
> access to your bank account!

:-)
Here is what caused me to ask how things worked for PHP:
http://www.fastcgi.com/devkit/doc/fa...intro.htm#8485

Thanks again.