On Apr 11, 2008, at 4:41 PM, Dossy Shiobara wrote:
Configuration parameters is too coarse-grained control.
You could allow control by mime-type and size, though I'd say all but
the shortest text/* files would benefit.
And the Yahoo best practices page referenced earlier suggests that ALL
text/* files will benefit, on average.
Computers are actually quite fast these days, and while dial-up
connections are becoming increasingly rare, the fact is that there are
bandwidth bottlenecks that slow the pace at which bits are transmitted
from your server to the user's browser.
You could also have an explicit ns_returnz for those who want finer-
grained control - leave compression off in your configuration file and
explicitly request it if you want it.
(IMHO, the decision to compress a request
should be handled on a per-request basis, as not all requests
unilaterally benefit from server-side compression ... so this should
be
an _intelligent_ decision that's being made by the developer whether
to
compress the result or not.)
This is more micromanaging of delivery that's really required, IMO.
Mostly you just want to make sure that only text/* or other
uncompressed formats are compressed.
----
Don Baccus
http://donb.photo.net
http://birdnotes.net
http://openacs.org
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
