Re: making filters more efficient

2004-03-04 Thread Greg Stein
On Tue, Mar 02, 2004 at 10:11:06AM -0800, Stas Bekman wrote: Justin Erenkrantz wrote: ... Correct. Because the EOS is generated by the request-level protocol handler (HTTP_IN). That's exactly how it is designed. If a connection input filter saw EOS, it'd signal end-of-connection not

Re: making filters more efficient

2004-03-04 Thread Geoffrey Young
If you have a concrete example of something that needs to query the state, then we can examine whether it should hook into the processing differently. I bet there is a different hook or approach that can avoid a query of the state. I think where stas is headed are cases like ryan's

Re: making filters more efficient

2004-03-04 Thread Stas Bekman
Geoffrey Young wrote: If you have a concrete example of something that needs to query the state, then we can examine whether it should hook into the processing differently. I bet there is a different hook or approach that can avoid a query of the state. I think where stas is headed are cases

Re: making filters more efficient

2004-03-02 Thread Justin Erenkrantz
--On Monday, March 1, 2004 10:58 PM -0800 Stas Bekman [EMAIL PROTECTED] wrote: An EOS *is* generated for this. It does in the request filter (in and out). It does in the connection output filter. It does *not* in the connection input filter. Correct. Because the EOS is generated by the

Re: making filters more efficient

2004-03-02 Thread Stas Bekman
Justin Erenkrantz wrote: --On Monday, March 1, 2004 10:58 PM -0800 Stas Bekman [EMAIL PROTECTED] wrote: An EOS *is* generated for this. It does in the request filter (in and out). It does in the connection output filter. It does *not* in the connection input filter. Correct. Because the

making filters more efficient

2004-03-01 Thread Stas Bekman
It'd be very helpful if Apache provided methods to query various in and out stream processing events to make filters more efficient. The events I can think at the moment are: - end of HTTP input headers - end of HTTP input body - end of HTTP response headers - end of HTTP response body only the

Re: making filters more efficient

2004-03-01 Thread Andr Malo
* Stas Bekman [EMAIL PROTECTED] wrote: 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 no other comments atm, but this isn't really ideal. The connection does not know anything

Re: making filters more efficient

2004-03-01 Thread Stas Bekman
André Malo wrote: * Stas Bekman [EMAIL PROTECTED] wrote: 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 no other comments atm, but this isn't really ideal. The connection does not know

Re: making filters more efficient

2004-03-01 Thread Justin Erenkrantz
--On Monday, March 1, 2004 8:18 PM -0800 Stas Bekman [EMAIL PROTECTED] wrote: It'd be very helpful if Apache provided methods to query various in and out stream processing events to make filters more efficient. The events I can think at the moment are: ... - end of HTTP input headers I'm not sure

Re: making filters more efficient

2004-03-01 Thread Stas Bekman
Justin Erenkrantz wrote: --On Monday, March 1, 2004 8:18 PM -0800 Stas Bekman [EMAIL PROTECTED] wrote: It'd be very helpful if Apache provided methods to query various in and out stream processing events to make filters more efficient. The events I can think at the moment are: ... - end of