Hello, at the moment the code splitting feature works like this: There is a main html/js code file that has a hashed name like "4F5D....html". The deferred code itself is placed in the directory "deferredjs/4F5D.../". Inside this directory one sees a lot of files with names like "1.cache.js" and so on. This technique is already quite nice and helps to reduce the initial loading time of many applications. The code splitting feature is also worth a million if one has parts of code that are only executed in some special cases (like configuration dialogs or dialogs for some group of people).
Now imagine that you have changed some code inside a deferred part. It is quite clear that the compiler has to recompile everything but I think it would be perfect if only the changed split point gets a new name instead of creating a new name for the main html/js code file and a new directory inside the deferredjs directory. This way a client browser would not have to reload the whole application but instead only the changed part of it. For this I propose to use another naming scheme for the deferred code parts: 4F5D....html is still the main file deferredjs/4F5D.../ is still the directory for the deferred code parts deferredjs/4F5D.../3D1E....cache.js would be the name of a deferred code part. deferredjs/4F5D.../index.nocache.js small file that contains references to the actual deferred code files like 3D1E....cache.js The last file is needed to have a static reference file which can be used by the main html/js file. It is clear to me that this proposal only works if the main code doesn't get changed but this feature would improve the overall user experience in most cases. Regards, Bernhard J. M. Grün -- 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.