On Sat, Oct 25, 2003 at 03:00:27PM -0600, Joshua Ginsberg wrote:
> Here is a patch to add another subcommand to ns_conn called state. It
> returns the current state of processing the conn:
>
> ns_conn state -> {"adp" || "tcl || "filter" || "trace"}
> proc ns_stop {} {
> switch [ns_conn state] {
> "adp" {ns_adp_abort}
> "tcl" {ns_tcl_abort}
> "filter" {return "filter_return"}
> "trace" {return -code return}
> }
> }
That sounds kind of interesting. But, is it subject to race
conditions? I have not examined your code, but my guess is that it
is.
Is it possible for ns_conn state to return "filter", then to finish
processing the filter and actually be in state "tcl" at the time you
try to abort the filter processing? If so what happens (what breaks)
when this occurs?
> The reason I wrote this patch was because I wanted to be able to write a
> library function stop all processing of the conn regardless of what
> state the conn is in. If the conn is in an ADP, you have to call
Why specifically do you want to call your ns_stop proc?
--
Andrew Piskorski <[EMAIL PROTECTED]>
http://www.piskorski.com
--
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.
