Exactly, it's a sort of a queue. Each time a task finishes, it invokes the normal onSuccess method, which in turn invokes the onSuccessImpl (where you would now put your logic). Once onSuccessImpl is complete, the next async call to the server is invoked.
Each call can be "daisy-chained" onto the previous one, it's basically just a linked-list of async invocations, and their return logic (in this case with a generic onFailure method thrown in for easier coding). Hope it helps, //Jason Parmeet Kohli wrote: > Wow Jason !! That seems like quite a solution .. Can you please help > me make certain that i totally understand it. The onSuccessImpl is my > core test step method right ? Something like simulating a queue is > this ? A queue of 2 test steps to be precise. The one executing > currently and the next one to be executed. > > Thanks !! > Parmeet > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
