I'm on the "synchronous calls are the wrong approach" side, but what would really be useful would be some utility classes that allowed "synchronous like" approaches.
Specifically : - an async batcher that given a list of async services calls all at once and then executes a specified action when all return (it keeps an internal count of async calls returned) - a serialized async batcher that calls a list of async services one at a time and then executes a specified action when the last one returns (each callback triggers the next async call) So you could block all (or part) of the UI with a modal overlay, call the async batcher and set the return action to fire an event to unblock the UI. I found this pattern helpful when loading data from different services while making the user wait till all the data has arrived. It can be a bit more flexible that building lots of services (and the returned objects) into one call. Regards, Carl -- 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.
