I do understand the mechanics of it; you post the form to the "please wait" page, then from there redirect to the final "confirmation" page where all the action takes place. I've managed to set this up and it works OK for me.
Michael,
I'm curious about this approach. When you do the redirect do you immediately lose your "please wait" text? In other words does the user momentarily see "please wait", then see a blank page until your long job is processed and can return some results? Or do you assume it will take X seconds and pause for that long before issuing the redirect?
Another approach is to hand the lengthy job off to a 4D process and track it's completion status. Therefore you don't go through an intermediate page but start off with a page that refreshes itself every few seconds with the tag like you cited
<meta http-equiv="refresh" content="1;URL=http://www.site.com/confirm.a4d";>
If the job isn't done you just display "Please wait" (or a nice animated status GIF) and wait a few seconds to refresh. Prior to sending the refreshed page you check to see if the job is done. If it is return the results. If not display your "Please wait" page again. Be sure that the final results page doesn't have the <meta http-equiv="refresh"... />.
The downside to my approach is that you have to write 4D code instead of being able to do everything in Active4D. But then again if its a really long job it might benefit from running as compiled code?
Brad Perkins
_______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
