No. "Waiting" in the browser means it freezes it (remember - single threaded). Why not just disable the input fields that can lead to an RPC call (& some kind of processing indicator so the user understands what's going on) & reenable them when the call completes.
Just apply a proper MVC pattern & you'r code should be clean (i.e. your controller will disable the view when the model is busy updating the backend & reenable it when the model indicates it is finished). On Mon, Apr 27, 2009 at 8:33 PM, AirJ <[email protected]> wrote: > > Hi GWT gurus, > > I have a generic questions regarding asynchronous calls. Basically in > our gwt web application, when user clicks on "save button", the > application launches a bunch of asynchronous calls(validation, server > side callbacks). > > "Save" should only be invoked when all those asynchronous calls are > processed. > > One way to do it is to call "Save" in the onCallbackSuccess() method > of those asynchronous calls. But it will make the code very > unstructured and hard to trace. > > Essentially I need a method to flush all the queued asynchronous calls > before I make a new one. Will > DeferredCommand.addCommand() solve the problem? > > Thanks, > Di > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
