Craig R. McClanahan wrote:
> That was exactly the original thinking -- create a servlet that would be able
> to execute external applications in conformance with the CGI spec requirements
> (principally related to environment variables, and connecting standard input
> and output of the application program to the request and response streams
> appropriately.
Excellent. I suppose the right thing to do now is propose a design to
this list with specification references for review. If that is too
heavyweight I can just run the code by somebody (you, Craig?) after
testing on my own Catalina build.
> Having this functionality implemented as a servlet means that you can map it to
> a directory path ("/cgi-bin/*") and/or a filename extension ("*.cgi"), in the
> same way that you would do so in a web server. Or, in a security conscious
> environment, you could just remove the mappings to make CGI service
> unavailable.
Exactly, and I suppose the directory path w/could obviously be web
app-specific, giving the normal encapsulation benefits.
Would there be any scope for extra web-app-related information being
available in the spawned-process' environment, so it (the CGI) could
figure out the context path, etc.?
> That would be great! I will sign you up for that item.
Thanks, I look forward to helping out; if I do something wrong please
let me know.
>
> Craig McClanahan
>
Chrs,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
