This is a lesson learned. The next release will have better
documentation for the community.
The idea of thread pools and allowing the dynamic changing of pool
settings is a great addition to the code base. The failures here
were 1) communication, 2) backward compatibility of the config settings.
As Nathan and I pointed out - it would not be a good idea to execute
the "ns_pools set default" command in the server config - but rather
in a Tcl file after the server starts - and use the cfg params. This
should have been added to the init.tcl file (where the Tcl files get
sourced) before the release.
Once Nathan, Dossy, and I have a chance to talk - I will add this to
the HEAD, document, and send email.
Michael
On Aug 1, 2007, at 11:43 AM, [EMAIL PROTECTED] wrote:
Nathan,
This has to be the most bizzar change to the configuration setup for
AOLserver, is it really true? Now you have to execute commands
inside the
config file to set this?
This is absolutely crazy. The init file has never required dynamic
execution of procs to work, and to have something this basic as an
exception is nuts.
Not to mention that breaking every bloody site's config file in the
process is rather rude.
Some of us still use AOLserver for production sites, hard as that
is to
believe.
Was there community discussion of this change before it was
implemented?
It represents a huge change in configuration philosophy.
Who's bright idea was this?
--
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.
--
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.
