Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Whats with all the cache/nocache stuff and weird filenames?

April 26, 2017cache filenames NoCache stuff weird

0

Posted

Whats with all the cache/nocache stuff and weird filenames?

1 Answer

0

Posted

During its bootstrap process, a Google Web Toolkit application goes through a series of sometimes cryptically-named files. These files, generated by the GWT Compiler, usually seem strange to developers new to GWT. 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. The important files produced by the GWT Compiler are: • .nocache.js • .gwt.rpc Each of the items listed above is described below. However, first it’s important to understand the concept of deferred binding since that notion is at the heart of the bootstrap process injected intto the .nocache.js file, so you might want to read a bit about deferred binding before continuing. Before explaining what each file does, it’s also 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