>From what I understand, code-splitting must be thought about in a method-by-method basis. That is, the variables you use is not important, but the method you call on it is. In short: - If all calls to methodA() happen behind the _same_ split point then methodA() will be part of that fragment (loaded only when needed) - If methodA() is called behind one split point AND behind another split point then it will be in the leftover fragment (likely loaded very early) - If methodA() is called at least once from a non-code-split path then it will be in the initial download
Cheers, Philippe -- 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.
