Actually from a user's point of view, hanging the UI is NEVER acceptable even if it is for less than a second.
In the case of waiting for a couple of seconds, depending on the browser and version, you cannot change tabs, cannot close the browser or anything. This is a VERY NAUGHTY thing to do intentionally. In the case of a network failure this frozen state lasts indefinitely, and that sort of thing really pisses off your users. particularly if the only way they an figure out how to exit your web app is to reboot their computer! Learn to divide up your application into the things that need to happen before the RPC is sent, and the things that happen after. place those things in their own methods, then call the "after" methods from your Callback. Your users will thank you for it later. -jason On Mar 10, 2009, at 10:28 AM, ping2ravi wrote: > Do you see any problem in having synchronous calls.? except that it > may hang the UI for a second and that is acceptable. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
