AFAICT, most Google Apps do on the server side what the *.nocache.js does on the client side in a "default" setup (i.e. choose the right permutation, i.e. the right *.cache.* file, to load for a given user agent, locale, whatever combination). They use the xsiframe (or actually probably a custom linker, similar to xsiframe) that generates *.cache.js instead of *.cache.html so they can include a <script src="…"></script> to it in the generated HTML. I believe their linker generates some sort of JSP code or similar, instead of the *.nocache.js that the other linkers output. That way, they save one round-trip to the server, and given that the host page is already non-cacheable due to authentication, they don't lose anything (in a "default" setup, the host page is a static HTML page, so you can generally enable some level of caching on it; what matters being that the *.nocache.js is non-cacheable).
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/wr0-FXA4axYJ. 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.
