Although AsyncProxy looks fancy and might look like a good idea at first, I actually think the due to potential unsafe usages and practicality reasons, it may not be a good idea to include as part of the core SDK.
The main reason for that is if the methods include logic then you cannot use it because you cannot simply stub the return with static values and similarly the call sites of the method just can't move on assuming everything worked fine. If there is no complex logic hidden behind the method then it is not a good candidate for code splitting. All these together I had hard time to find much practical and safe usage in the past and that it is still true for me today to favor it over direct usage of GWT.runAsyncCode. Actually, today I noticed that there is no a single reference to it inside Google, this an evidence to my hypothesis as the code is out there more than 5 years. But before going forward, I would like to hear about your practical experience with it and see if it makes sense to keep it part of the core SDK. If we decide to move forward, I will deprecate the class with 2.6 release and after the release I'll create a separate 3rd party project for people who still would like to continue using it. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
