There is a new filter point for ns_register_filter called prequeue. It isn't very useful because it runs in the driver thread, blocking the loop until it finishes with all prequeue filters that match. (There may actually be spins wasted on every request looking for matches, haven't checked that.)
But it is there and I used it for some testing. What I found out is that it causes a massive memory leak, about 1.5MB per request. Maybe an interp is being stranded with every request or something. Anyway, just a note that this feature isn't consistent with the other filter points, and has serious problems. The good news is that it is easy to identify. Your machine will eventually grind to a halt. 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.
