Re: Client side caching of the .nocache,js and other included .js and .css files

How about ETag ? This should work out of the box with any tomcat.

On Oct 9, 8:16 pm, PeterT <PeterTeunis...@verizon.net> wrote:
> We have a project.nocache.js file that included other .js and .css
> files. The generated project has a long GUID like name which changes
> each compilation, so that file is correctly loaded, but the problem we
> see is that when we change the other include files on the server, the
> client does not get the new files.  For the .nocache.js file we can
> force a reload by passing an additional parameter on the url that we
> change everytime the server side changes, but that does not cause the
> included .js and .css files to be picked up.
>
> Does anybody have the same issue and are there ways around this?

--
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.