> FastCGI is not a wonderful solution, but it is *a* solution ... Ugh!
>> Something to think about: the various phases of serving an HTTP >> request. > 1. server initialization. > 2. connection received. 3. HTTP command received. > 4. Headers returned. > 5. Content returned. > 6. Connection closed. > 7. Post-connection processing. Seems to me that returning headers and content is effectively the return value from the handler in phase 2/3, eh? The other APIs (Apache and NS) define phases to do stuff like authentication etc. Do we want support for that? Do we want to tie it to Apache (in which case we can talk about things like htaccess, logging, integrating with httpd.conf etc.) or make it general? -s _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
