Monday, June 18, 2012

Re: GWT offline

> We had the same problem. But instead of doing what you did, we found in the
> doc that the nocache.js file should be returned by HTTP servers as
> non-cachable. This solves the issue. You just write a servlet that sets
> Headers when delivering that file.

OK but I don't understand. Isn't *.nocache.js needed to bootstrap
(i.e. load) the GWT code?
If *.nocache.js isn't cached by the browser, then how does the offline
version load -- [it can't get it from the server!!!]?

If I have extra time to try an offline version that hasn't set a
backup to load I will. I don't see how it would work though unless
the browser is 1) really storing *.nocache.js [even though you set the
header in the servlet not to] and just refreshing it everytime or 2)
not really needing *.nocache.js. I don't think either of those things
is true but I can't test it right now.

Shawn

--
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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate