Synchronous RPC is a tremendously bad idea. Read this for more insight: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/faca1575f306ba0f/3be719c021aa19bd
The way I have addressed some of the problems you mention is with an event-based model. For example, to display the results of getUserAddresses(), I might have a ListBox widget backed by a model of some sort. The list and model are tied together with event listeners such that clicking in the UI updates the model and changes in the model (adding and removing addresses, say) are reflected in the UI. In such a setup, the completion of an RPC will eventually trigger a model event that causes the list to redraw itself. Working this way solves a lot of problems because most of my code is decoupled from the RPC details and I don't have to worry about RPC being synchronous or asynchronous. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
