On 2006-04-27, B Wooster <suppressed> wrote:
> I've seen people use Javascript (changing text on a page), using
> redirects, etc to handle the case where a "please wait" screen has to
> be shown on a submit.
>
> Are there best practices on doing this with CGI::Application?
One pattern to address this was proposed by Randal Schwartz in 1997:
http://www.stonehenge.com/merlyn/WebTechniques/col20.html
Simplified:
Fork the long running process into the background. This process
can report its status to a file as it goes.
The page that the user sees can refresh it periodically, checking the status
via the file and reporting back to the user.
I've used this kind of pattern successfully myself.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
suppressed Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.