> If you don't call ns_adp_abort, the page will continue executing. > Take a look at the following example: > > <% ns_returnredirect /someotherfile.adp > ns_log notice "still going..." %>
I just came across something interesting about this and noticed a few points and have a couple questions: 1) ns_adp_abort is no longer in docs 2) Is the difference between ns_adp_break and ns_adp_abort? a) break returns data currently in buffer b) abort stops processing and returns no data c) I believe ns_adp_return just goes up 1 on the call stack 3) If you are processing a ns_register_proc for an url it doesn't seem to allow you to any of the 3 calls after an ns_returnerror/ns_returnfile/etc What is the prefered method of jumping out of the callstack if you are in i registered proc for an url? I had never before seen an error processing ns_adp_break/return/abort before this. I can deal with this problem but found it interesting. Best Regards, Carl -- 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.
