Carl, Your proposal is interesting. But as a user, if I have to wait, I leave... So many be an application needing some "wait a minute" popup is not a good approach for the future. Imagine your browser putting a popup each time a page is loading. Tabs will become useless, multi- core computer too and so one...
Okay, it's not easy to do such application without popups. And I'm the first to use popup ;). But it can be really, really better. Olivier On 28 mai, 06:36, Carl Pritchett <bogusggem...@gmail.com> wrote: > 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
