Hi, I'm thinking about using Code Splitting a little differently from the normal use case: What if I could take a bunch of large classes that basically never change - like e. g. HashMap and HashSet - and split them out into a fragment that can be cached forever. This fragment's MD5 sum shouldn't change. So when I release new versions of my app frequently, the users don't have to download these classes again.
Such a fragment could be loaded a) Together with the initial download fragment b) Together with the leftovers fragment ...depending on if I need HashMap and HashSet for my initial download or not. I don't think, that's possible now (or is it?) Thanks Chris
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.