On 2008.04.13, Don Baccus <[EMAIL PROTECTED]> wrote: > Or just put back the config parameters as they were, they worked fine > for everyone for a decade. I don't remember the masses shouting that > the config approach wasn't sufficient. It suddenly appeared without > discussion nor documentation.
Uh, either your memory is poor or you need to review the mailing list archives again. The number of times people have asked "can I change [a particular setting] without requiring a nsd restart" and have been given the answer "no, config changes require a server restart" has indirectly suggested that if we can move something out of the config and into the runtime environment, it would be preferred as people ask for it repeatedly over time. Being able to tweak and tune thread pools at runtime has come up many, many times. Each time, the answer is: change the config setting and restart, which usually wasn't desirable because restarts during the day on a production system weren't something folks could do ad-hoc, as they were running a single server, not load-balanced ... Seriously, this has been a long-standing ask, to make more config settings modifiable at runtime. Perhaps the way compression has been implemented wasn't perfect, but it was a start, and I think Jeff's suggestion of shipping a filter proc that enables compression server-wide by default is the right answer. Making the setting purely config-driven is just perpetuating the "sorry, config settings need restarts" problem. -- 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.
