At 02:06 PM 24/09/2001 -0700, Shamim Mohamed wrote:
>There is some discussion floating around about passing env. variables
>etc. to a socket server based app. server. I think that's a huge can
>of worms and should be avoided. CGI is a hack that needs env. variables
>because of its "external program/stdin+stdout" model. An intelligent
>design would do something like invoke callback procedures (whether
>linked in a la Apache DSOs or part of an app server in a sister process)
>for various "phases".
I was going to look at implementing a FastCGI module for Unicon. FastCGI is
not a wonderful solution, but it is *a* solution and a working one at that.
The protocol is documented, so I just have to go coding and make it work! :-)
>Something to think about: the various phases of serving an HTTP request.
Maybe we could start with this:
1. server initialization.
2. connection received.
3. HTTP command received.
4. Headers returned.
5. Content returned.
6. Connection closed.
7. Post-connection processing.
Phases 2 and 3 could be combined, perhaps.
Wade.
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group
