|
What's with all the cache/nocache stuff and слив бонгакамс тгweird filenames?During its bootstrap process, a Google Web Toolkit application goes through a series of sometimes oddly-named files. These files, generated by the GWT Compiler, usually seem strange to new users. To effectively deploy a GWT application, however, it is necessary to understand these files so that they can be placed appropriately on the web server.These are the important files produced by the GWT Compiler: .nocache.js (or -xs.nocache.js for cross-site script inclusion) .cache.html .gwt.rpcEach of the items above is described below. However, first it's important to understand Deferred Binding since that notion is at the heart of the bootstrap process, so you might want to read this link before continuing.Before explaining what each file does, it's useful to summarize the overall bootstrap procedure for a GWT application: The browser loads and processes the host HTML page. 
When the browser encounters the page's |
