On Sun, May 05, 2002 at 06:26:53PM -0400, [EMAIL PROTECTED] wrote: > The filter should remain regardless of whether there is a C-L, because we > use that filter to determine exactly how much data was sent through the > filter stack. That is useful information, and it doesn't hurt performance > in any meaningful way (We are just looping through the brigade). However, > the filter should be smart enought to leave the C-L alone, unless it is > required.
Okay, I guess. I do think it'd cause a performance hit though. But, I won't push it. I don't see the need for it though. However, I'm more concerned that we'll be buffering data on HTTP/1.0 requests that already have a C-L. This would be enormously expensive when we could have streamed the data to the network rather than holding on to it until EOS is seen. -- justin
