At 10:05 PM 26/09/2001 -0700, Shamim Mohamed wrote: > >> 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?
That would be one way of looking at it, yes. >The other APIs (Apache and NS) define phases to do stuff like >authentication etc. Do we want support for that? Hmm. Might be worth considering. It also occurred to me that there are some sub-phases between 3 and 4, to do with converting a URL to a filename. I know from the mod_rewrite docs that Apache has some hooks at that point. >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? I think some of those could probably be suitably abstracted anyway, but not having used any other web server than Apache (IIS doesn't count), I don't know. Wade. _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
