On 14.10.2007, at 23:34, Stephen Deasey wrote:
Did you eventually use this code? Did it work for you?
It is still lab quality. I have it running here for
some time but not in the production (i.e in the product).
I guess it is safe but you obviously never know. I also
have no speed metrics
The only thing which broke my old code regarding switching to vsnprintf
is that old Ns_DStringPrintf handled empty string differently, vsnprintf
now puts (null), before that empty string did not put anything.
I still need to review si the damage is critical enough or never upgrade
until all
On 10/15/07, Vlad Seryakov [EMAIL PROTECTED] wrote:
The only thing which broke my old code regarding switching to vsnprintf
is that old Ns_DStringPrintf handled empty string differently, vsnprintf
now puts (null), before that empty string did not put anything.
I still need to review si the
On 10/15/07, Vasiljevic Zoran [EMAIL PROTECTED] wrote:
On 14.10.2007, at 23:34, Stephen Deasey wrote:
Here's the thread from last time (lots of good ideas):
Yep. Too bad nobody peeked at the suggested
(bare-bones) implementation. I guess I should
just go and get it in, tagging the tree
On 15.10.2007, at 20:37, Stephen Deasey wrote:
One problem is that there seems to be a lot of memory allocation and
copying going on, even on the fast path. For example, NsConf_GetBool()
does three mallocs, a couple of copies, conversion back and forth
between string and int rep, two hash
Vasiljevic Zoran wrote:
Do you have some other idea how (if) we should build the chnageable
config? It seems pretty silly to me that we need to restart the server
to change some marginal parameter... In the 21. century...
However this gets resolved, I think there should also be a way to
In the version we did for AOLServer 3.4.2, which relies on our
proprietary event-notification subsystem, we:
(1) Put a place in the startup .tcl script where over-rides from a local
file would be used (using source). That way, the file output from live
settings could be the equivalent of:
On Mon, Oct 15, 2007 at 12:53:57PM -0700, Jeff Rogers wrote:
However this gets resolved, I think there should also be a way to easily
write out a config file based on the current dynamic configuration, so
that if the server does get restarted the configuration can stay the same.
Excellent
