Assuming you can't make the code run faster, one technique I've seen done is to have the the RPC return when the job has been submitted. The user can then check on a "jobs" page to see a list of jobs from a database. Unfinished jobs can say "processing" until the server side has updated the list that it has completed/failed/etc. Save the results on the server side (possibly write the bare minimum needed to construct the final object, whether it's a report or a rendered image, etc) and for finished jobs on the jobs page, selecting a finished job will stream back the finished binary/display a widget/etc.
On Tue, Aug 11, 2009 at 3:43 PM, lakshmi thyagarajan < [email protected]> wrote: > Hi, > > One of my server side methods requires about 20 minutes to complete > (involves executing a series of scripts and a whole lot of iterations to > execute a complex algorithm). > An asynchronous call to this method from my client does not return back to > the client even after the method finishes execution. My GWT application is > deployed in a Tomcat server. The session expiry time in the tomcat server is > set to 30 minutes. This problem however does not exist in the hosted mode. > Could any of you help? > > thanks, > Lakshmi > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
