Well it depends on what you're doing and what you're trying to accomplish. I used Async gateways to spider websites. On my calling page I essentially checked if the spider was running, if it wasn't I instantiated it, if it was I told the user. If it was done, then I displayed the results. They could reload the page or come back 30 minutes later and reload the page to see if it had finished.
Jason Cronk
"Cody Caughlan"
<[EMAIL PROTECTED] To: [email protected]
> cc:
Sent by: Subject: RE: [CFCDev]
Asynchronous Process
[EMAIL PROTECTED]
one.org
11/11/2005 03:33
PM
Please respond to
CFCDev
Isnt that the whole problem, you have to wait for the async request to
return before you can do anything? Probably the best thing to do is
fire-and-forget the async request, have it update the DB and then later use
AJAX to display it when the DB is populated (using AJAX was noted
previously, this sounds like a good approach).
/cody
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
