- end of HTTP input headers - end of HTTP input body - end of HTTP response headers - end of HTTP response body
only the latter is sort of accessible via the EOS bucket (which as I've pointed out in another email is not always set!).
Ideally the connection record could have the following entries:
done_with_input_headers done_with_input_body done_with_output_headers done_with_output_body
so for example when http headers processing is completed, the done_with_input_headers flag will go up. etc. These flags will be reset at the end of each request.
At the moment it's sort of possible to workout all these events from the filter itself, but it's *very* inefficient and makes the code fragile if Apache needs to change the internals. Matching for /\n\n/ on every bucket just to know when the headers are done with, is just plain bad, when the Apache core filter knows already when this event happens and it could share that knowledge with other filters.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
