The way to do it finally was: 1. inline nocache.js as a <script>...</script> in the module html 2. replace all string references of 'xyz.cache.html' to 'path/to/gwt/ output/xyz.cache.html' 3. (for RPC only) copy the serialization policy files to the module html location
On Aug 4, 9:02 pm, George Georgovassilis <[email protected]> wrote: > So, while trying to squeeze out the latest tiny bit of speed for my > application I ended up with this setup: > > index.html ( = module page) contains inlined css and the nocache.js. > The index.html is non-cacheable, but is guarded with an E-Tag, which > doesn't do anything to first time users, but recurring users will see > a 304 (not modified) and the application will load instantly. I > inlined the CSS so that no further HTTP request is neccessary, the > same rationale goes for the inlined nocache.js > > So the only HTTP requests are: > 1. load the index.html > 2. load aspriteimage > 3. load the browser dependent *.cache.js > > The problem here is that since I inlined nocache.js, now index.html > has to reside in the same location with *.cache.js, which is horrible > to configure for caching since I'm not using Apache but just Tomcat. > > Using a <base href=""> to bend the base location seems to work only on > Firefox, IE can't find its RPC services and Safari won't load at all. > > Any ideas? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
