Most of the changes are good, if you ask me. But one change gave users some trouble, that being the ns_pools API. The API itself is no problem, but there was a missing script for loading the existing threadpool configuration. But my biggest gripe over the new API is that it allows one virtual server to adjust the settings of any other virtual server. In addition, threadpools (and their threads) can be shared between virtual servers. When this happens you get threads with multiple interps, one for each virtual server, which seems counter to the desire to limit resources. When one of these threads exits, you lose all interps, so the startup time is also increased.
More than anything, the new changes lack documentation, and given that, I think that the most pressing need for the AOLserver community is to explore and document the new changes before any new work is begun. If specific API are going to get an internal adjustment (potentially ns_return), we should put some effort in beforehand to document the current behavior, and figure out the best way to make the change. This is true with compression. I think Brett has a good outline of how things should work, but the details will be important. Btw, I've looked at ns_zlib and there doesn't seem to be an internal hook into this. Brett, do you have links to how compression is supposed to happen in HTTP, and/or any test cases? tom jackson On Monday 14 April 2008 07:13, Jim Davidson wrote: > I'm the one that made most of "assumed good" changes to AOLserver 4.5 > -- my fault. Seemed like a good idea at the time. Is there a > complete list of changes to right that wrong? I may be able to hack > in the fixes quickly -- I'm just not sure the scope because I'm way > behind on the mailing list. > > BTW: I like config-based control of compression. Also, there's some > cool ADP caching stuff in 4.5 that let's you dynamically update just a > few parts of an ADP, leaving the rest pre-compiled for a time. Not > sure if folks have been using/testing that. -- 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.
