The segfault is obviously a bug... I think what's being referring to is
the behavior that allows code to continue executing after an
"ns_returnredirect" unless an "ns_adp_abort" is explicitly specified.
- n
[EMAIL PROTECTED] wrote:
And the segfaulting when you do this? Also a feature? I'd call it a
bug. Nothing you can do in an adp, scheduled proc, etc, etc (plain
tcl) should cause the server to crash.
Rusty
Titi Ala'ilima wrote:
It's not a bug, it's a feature. Seriously. Sometimes you want to
return a response to the connection and then continue processing
afterwards. Or at least, sometimes _I_ want to do that. :-)
-Titi
-----Original Message-----
From: Daniel P. Stasinski [mailto:[EMAIL PROTECTED] Sent:
Wednesday, September 06, 2006 2:10 PM
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] internal server redirects
it still crashes.
Ok, I just found this on the new docs....
NOTE: The script does not end at the time this command is invoked.
ns_adp_abort or ns_adp_return should be called to end script
processing after ns_returnredirect
This does stop the crash but I would still consider it to be a bug.
Daniel
--
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.
--
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.
--
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.
