I guess adding the ability to manage pools from the config does not
take anything away from the ability ALSO manage pools from a package/
module. Gives folks a choice.
M
On Aug 1, 2007, at 6:24 PM, Michael Andrews wrote:
Tom - I'll take a look at the code in more detail this week. Here
are my initial thoughts:
One of the benefits of having a Tcl command to manage pools is that
you do not need to use the server config. A Tcl module or package
can 1) create a pool, 2) register the pool, and 3) throttle the
params as needed at run-time. The only reason to do the pools.tcl
was to set the default pool's params with that from the config in
an attempt to make it backward compatible.
So personally, I think a "foo" pool would be better off created and
managed by a "foo" Tcl package or module. The config then stays
clean - and all "foo" logic and needs are encapsulated, easer to
rev/update/release etc.
Thoughts?
M
On Aug 1, 2007, at 5:39 PM, Tom Jackson wrote:
I've just confirmed maxconnections from an old config file,
although I guess
the real answer would be in the C code.
Are you going to commit my additions to the file?
tom jackson
On Wednesday 01 August 2007 14:21, Michael Andrews wrote:
I'll install 4.0.10 this week, confirm the param, and change if
needed. It is probably time to do a better base.tcl (server.cfg)
file. I will do that this week too.
--
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.
