Thank you both for your prompt and attentive replies. I was fearing the answer I got from Shawn as it looks it won't be possible to partially fetch a long collection from the server (and then fetch items on demand). The classic collection/list interfaces don't have the notion of "not available yet" embedded in their method definitions so even if you cache a big nr of items coming from the server initially, there is no guarantee the client won't consume those faster than the connection can handle ... which obsoletes the solution proposed by Lazo (I had the same idea initially).
So, all classic collections (and other classic alikes) would have to be be fetched totally before their construction ... argh! ... Or maybe my reasoning is wrong? Thanks again, Andi Mullaraj On Oct 16, 12:59 pm, Lazo Apostolovski <[email protected]> wrote: > Just a little change. You need to remove command from list before call > execute(); > > On Oct 16, 1:48 am, AndiMullaraj <[email protected]> wrote: > > > There are cases when blocking calls to server are indispensable > > (agreed, assync calls are the way to go for 99% of the cases). > > > I scanned the client API and cannot find a way on how to do this. If > > not through a direct API call, is there a way on how to achieve this? > > (Like having a wait/process_events loop going until the response comes > > from the server). > > > Thanks for you attention, --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
