We have a similar architecture at my work where those long reports are sent as an Async request (Async Gateway) and then user is notified via email when reports are complete.
Thanks On 12/21/06, Christopher Jordan <[EMAIL PROTECTED]> wrote: > > This probably isn't what you want either, but... > > You could have your report program write to a table when it's complete. > The record would consist of who needs to be notified, and the status of > their notification. Maybe the session ID or some session variable could > be stored. > > Then you could have a javascript function that you include at the top of > every page (like from the Application.cfm) that fires off an ajax call > to check this table for the presence of finished jobs that belong to the > current session or user or whatever. > > Does that sound feasible? > > Cheers, > Chris > > Brad Wood wrote: > > Ok, so I am working on some very long reports and am peddling ideas... > > > > > > > > Here's the idea: The user runs a very long report, and the request will > > simply be placed in some sort of queue to be ran asynchronously. The > > user is told he/she will be notified when it is completed. > > > > Then the user surfs away to another portion of the site. Half an hour > > later when the report finishes, a message pops up on the users screen > > saying "Your report is finished, you may view the result now". > > > > > > > > My first thought was I could place a receiver JavaScript function in > > every page in the site, then make an Ajax call to run the report. When > > the Ajax call returned, it would fire the function and display/alert the > > message. > > > > > > > > Well, no dice on that. I tried it in IE and FF. IE actually leaves the > > TCP connections open until the call returns, but there is nothing > > listening to receive it. FF actually threw an unhappy error when I > > tried to navigate away while the call was going, and then it closed the > > TCP connection. > > > > > > > > I'm really afraid the correct answer to this is "The web is stateless. > > What you need is a client server app. Convert your entire site to Flex > > 2 Enterprise and use their sweet messaging services and all your woes > > will disappear" > > > > > > > > Now, as much as I would like to do that, that's not really an option > > right now. Any suggestions? > > > > > > > > ~Brad > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:264753 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
