to load code asynchronously does not make sence unless not loaded by "demand", as a sample:
if you have login-screen as a first screen, and after login you want to initialize the application,here you would benefit from splitting the code, one part to handle login and the other for entire application, because you never need entire application code as long as you have not logged in successfully On 13 Aug., 21:52, Joe Hudson <[email protected]> wrote: > Hi, > > I'm wondering if I still get the benefits from code splitting from the > example below: > > String className = MyClass.getName(); > ... > GWT.runAsync(new RunAsyncCallback() { > onSuccess() { > new MyClass(); > } > > onFailuare() { > ... > } > > }); > > Basically, I am wondering that since I referenced MyClass.getName() > prior to the GWT.runAsync, does that kill the benefits I would get > from code splitting if I am trying to load all of the code related to > MyClass asynchronously. Thanks. > > Joe -- 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.
