Steven, If you are assembling a lot of web service results into a single result, it might be a good idea to sidestep the complexity of that on the client by letting the server proxy the requests and send a single result set back to the client. There might be a small performance benefit as well.
Walden On Aug 29, 5:18 am, Len <[EMAIL PROTECTED]> wrote: > Hi > > the onsucess of the web services calls you are waiting for could > update a "central call result registry" - i.e. a "singleton" that > keeps track of how many results are being waited for - which it knows > cause its been told when the calls were dispatched - and when the > required number is reached it can dispatch a further command to update > the ui as required ? > > Something like that :) > > Len > > 2008/8/29 Steven De Groote <[EMAIL PROTECTED]>: > > > > > > > Hi, > > > I'm having a bit of trouble solving an issue I have with asynchronous > > server calls. > > Currently, I have a panel which retrieves some data from a webservice, > > and in onSuccess I build the datastore to show my data table. > > > However, this should be changed that my table is only built after the > > completion of 2 different webservice calls (possibly even more). > > > Any pointers how I could attack this problem would be greatly > > appreciated! > > > Thank you, > > Steven- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
