Forum OpenACS Development: Calling ad_script_abort from within ad_returnredirect

Is it possible for the script to continue to run after the redirect? That is, if some long running query or other process needed to run, is it possible to redirect the user so they don't have to wait, and then finish processing?

The short story of the matter is that Don arrived here in the office and he was jet lagged and went back to the hotel for a nap. Then all of a sudden Mohan told me Don was posting in the forums again. I was wondering how even someone like Don would manage to do that while sleeping in an unconnected hotel room until I realized that I was Don...

So, back to the issue at hand. I guess I'll try to make the change and add the -no_abort flag that Jeff suggested.

Personally I like the idea of -no_abort since it makes the most common behaviour the default, but I'm not putting my hand up to crawl through every use of ad_returnredirect to see if it's required or not... :)

This change would be a mere convenience. Changing an api in an incompatible way for future convenience doesn't seem right. Either change the api in a compatible way, or create a new command, as suggested by Tilmann. My suggestion was for a default that produces the same behavior as the current command. I would prefer a new command to a change.

On Wed, Apr 09, 2003 at 02:32:33PM +0100, Peter Marklund wrote:
> Hey Andrew!
> I take your point, and it's good. However, please note that this kind of
> tone in our forums does not invite beginners to ask questions. Mohan

[shrug]  Well, you're entitled to that opinion.  My tone is usually
much more helpful, even (especially?) to clueless newbies who don't
know what they're doing, as you can see from my posting history.  In
this case, the tone seemed justified to me, even necessary.  Why else
would I post an essentially redundant comment, after all?  For
emphasis.

> Pakkurti has talked to several developers in Europe who have confirmed
> that this is a real problem that we have.

Rumor and hearsay.  If we're going to go by anecdotal evidence (which
in this case is probably fine), we should at least know the full
details of the anecdote.  And any such discussion probably belongs in
public on the BBoard, not here.

Tone and culture cut both ways.  I would hope that NO developers
trying to use and/or contribute to OpenACS consider themselves
"incompetent".  If they do, well, I don't think we want them, do you?
(Of course, the truly incompetent never consider themselves such, but
that's straying of topic...)             

Further, IMNSHO, the OpenACS BBoards show an unusually high degree of
both competence and helpfullness on the web.  High signal to noise
ratio.  That's why I like it so much.  I could be wrong, but in
general I don't see any "tone" problem.