Paul Querna wrote:
Yup, I have pretty much not done any work on a local FastCGI process management so far. I figure once we have the wire protocol down, adding all the process management stuff is a whole different project.
I am keen to find a way of running the CGIs as different users depending on what user was authenticated on the frontend.
There is the simplest case of a one to one mapping (user logged in corresponds to a user on the backend) to many to one (user in a group on the frontend corresponds to a group user on the backend).
I personally like a background process, that takes care of managing all the backend FastCGIs, kinda like mod_cgid. The one major thing I would change, is for Unix Platforms, you would use unixd sockets, to connect from the worker to the fastcgi Backend, to avoid the overhead of a 3rd process proxying it.
This sounds like a job for the filter stack being able to deliver data to and from a socket in addition to to and from a tcp socket.
Fastcgi should in theory not care whether it's TCP or unix sockets, it would be down to some kind of URL?
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
