httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@covalent.net
Subject Re: woah, "GET /" with autoindex
Date Sun, 07 Jan 2001 21:04:25 GMT

> since the underlying ap_bucket_putstr and ap_bucket_printf are implemented
> as one-copy, coalesce will result in a two-copy implementation... which is
> less than 1.3's one-copy implementation.
> 
> not to mention that the current ap_bucket_{putstr,printf} result in far
> too many ap_bucket_ts being allocated.

But like I said, those functions aren't being used in this case.

> p.s. what's the syntax for turning on a filter?  or should i rtfm?

ap_add_output_filter(FILTER_NAME, NULL, r, c)

in the code someplace

OR

AddOutOutFilter COALESCE

In the config file.

Ryan

> 
> On Sun, 7 Jan 2001 rbb@covalent.net wrote:
> 
> >
> > > 1.3 would generate three 1448 byte packets plus one straggler.
> > >
> > > on linux you could CORK in 2.0 and unCORK at the end and it'd generate the
> > > right packets... but that's not portable.  so the fix needs to live
> > > somewhere in the i/o layering... which i'm not familiar enough with yet.
> >
> > Try looking for the COALESCE filter, and turning that on.  This should fix
> > the sub-optimal packets.
> >
> > Ryan
> >
> > _______________________________________________________________________________
> > Ryan Bloom                        	rbb@apache.org
> > 406 29th St.
> > San Francisco, CA 94131
> > -------------------------------------------------------------------------------
> >
> >
> 
> 


_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------


Mime
View raw message