Andrew Steets schrieb:
The patch I sent earlier seems to fulfill these needs, but I am
worried about corner cases where LogTrace (from the nslog module)
could blow up. Nothing about the state of the Conn * seems to be
guaranteed when the ConnCleanup callbacks are called.
Dear Andrew,
i think most (all?) of the repondents seems to agree that writing in the
about case to
the access log file. For me there are still two quesions open:
a) is it possoble to call ns_adp_abort at some time, where the server
might crash
(in normal operations, everthing looks fine to me, problems might
occur in
when called from some traces; other calls are likely to have similar
problems)
b) the patch replaces the call to the regular server trace by a
connection cleanup call.
this means, at least in 4.5.*, ns_adp_abort seems to cancel all
traces (also
these registered with ns_register_trace). Is this desired?
From Tom's website: http://rmadilo.com/files/nsapi/ns_adp_abort.html
the doc of ns_adp_abort says
... Every ns_returnxxx call in an ADP should be followed with a call
to ns_adp_abort....
With this recommendation, cancelling traces seem wrong to me; or at
least,
this should be documented.
We don't use traces, all of OpenACS does not use it, so this is no
current issue for us.
-gustaf neumann
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<lists...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
