On 2008.04.11, Don Baccus <[EMAIL PROTECTED]> wrote: > On Apr 11, 2008, at 4:06 PM, Tom Jackson wrote: >> Regardless of whether this gets integrated with ns_return, or as a >> config, it >> is much better to start out with a new API, such as the ns_returnz or >> ns_return_compress. > > I would much rather have this be controlled by configuration parameters. > We want to be able to write code for distribution using ns_return, and > allow those who deploy it to control whether gzip compression is used or > not when they configure their service.
Configuration parameters is too coarse-grained control. Ultimately, the compression flag should be conditionally turned "on" in a registered filter if you want it at a higher level than in the actual request processing code, itself. (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.) My two cents, anyhow. -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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.
