In which fashion you mean safe ? If it is about internet security, it doesn't hurt or make good - the code will de downloaded by the client across the net and he can look at it. If it is about safe threading, f.e. to avoid two rpc calls at same time, the caveats must be resolved by your code before.
You would use the static way if + You use the call a lot of times in your web app ( f.e. a getActualData() call ) + You love simplicity You would generate the instance every call if you: + Use the call only once ( f.e. login() ) + Want to call different servers or urls for the same RPC - take in account Same Origin Policy Take in mind that the AsyncCallback object is the one you're using new ( or maybe not ) at every RPC call, so it's better to use the static way by default Oskar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
