* Graciliano M. P. <[EMAIL PROTECTED]> [2004-02-04 20:54]: > Soo, in the cgi-bin, let's say, you have a binary built in C, > that make a socket connection (or nay other IPC) to a another > process that is a Perl script that will receive all the %ENV > that Apache send, soo the script can simulate that is inside > Apache.
I'm not sure how viable it is to offer something written in C to people without shell access. Unless you want to offer dozens of precompiled binaries and have access to that many platforms to test on, this'll require compilation at the user's end. Although I do like the concept of having a very lightweight binary serve as the actual CGI program. (I'm not sure how close to FastCGI this is, though, never having looked into that one in detail.) > Soo, what name I can give for this? I just have no idea. > > - CGI::FastBridge? Hmm.. I think "fast" doesn't need to be in the name. To me the important bits seem to be that a) the Perl interpreter and thus the CGI program runs persistently as a server of sorts and b) it communicaes requests/responses by IPC with an external binary. Sounds like CGI::IPCServer. -- Regards, Aristotle "If you can't laugh at yourself, you don't take life seriously enough."
