On Sun, 2004-03-07 at 23:37, Zoran Vasiljevic wrote: > Oh, it is not the work that I'm afraid of :) > Your idea seems pretty good. The only thing here would be: how > to treat non-connection threads? Those are not aware of any URLs. > We have usually a dozen of those performing all sorts of non-page-serving > tasks. How would you distribute the log info from those threads? > Nevertheless, it is a good idea. I will play with this mentally > and see if it can be extended to cope with all thread logging. > Thanks for the hint.
Shoot, I was hoping you wouldn't notice that point! ... Actually my idea only addresses one way of registering a way of selecting then setting the channel, all the work you were going to do would still be required, but my idea might interfere with yours... unless you had a separate command ns_log_tochannel, for instance that would be the underlying command??? Or maybe a better idea is to come up with a way of establishing a hierarchy of commands/script files and log based on that criteria instead. If procs were namespaced, a message from a certain namespace could trigger the desired action. Or while loading, library commands could be associated with the files where they were stored... Dunno, but your idea of logging to separate channels sounds very good. tom jackson -- 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.
