On Sunday 07 March 2004 07:41 pm, you wrote: > On Sun, 2004-03-07 at 04:03, Zoran Vasiljevic wrote: > > Like, for example: > > > > set chan [open /some/file.log w] > > ns_logctl pushchan $chan > > ns_log notice "This goes to chan $chan" > > set chan [ns_logctl popchan] > > close $chan > > Interesting idea, but it this a per-thread stack? I'm guessing the > motivation is for performance, what if you could register log files like > you register "Registered Procedures", use the trie structure to store > nearest match logging. Then on restart you could easily add/remove a log > file for debugging purposes, or long term high performance logging. >
Oh, misunderstanding... I was talking about the *server* log not the access log. The motivation is not the performance. The motivation is to be able to collect (even over the network) logs produced by many AS instances running all arround the net at one central place. Oh, the stack is thread-wide of course. The ns_log itself is a thread-wide stuff, therefore. We use ns_log facility extensively and need it for various debugging purposes. It proved very clumsy to handle all those logs dispersed on different machines arround the net, so we thought about creating a Tcl channel and sending all the output to one central handling place. Now, one could employ the same principle to access logs as well. The only thing is: I don't know wether there is Tcl access to access logs (I think not). The ns_logctl functionality appearing in 4.0 was a good step towards better server log management. It could be extened even further, as explained in my proposal. The good thing here is: there is no backward-compat to take care of, no users would be affected by this change so there is nothing to fear about. It merely adds new functionality. For some people this may be interesting, for some not. Therefore I wanted to probe wether anybody could benefit from this. We would, definitely. Cheers, Zoran -- 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.
