You said you didn't want to chain calls. If you make more than 2 calls to the server, then the 3rd one onwards will be delayed.
The quickest and most efficient way is to do the work on the server in one call. The maintenance is no different, in fact it is easier, since you don't have to bother with all the internet traffic. Why is it not a good idea from the architecture pov? Ian http://examples.roughian.com 2009/3/10 ping2ravi <[email protected]> > > Ian, > That is not an option for me, creating such API is not a good idea > from application maintenance as well as architect point of view. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
