Re: IncompatibleRemoteServiceException after new deployment

Even static pages are changed once in a while. IE tends to keep on to the cached version until you restart the browser window or you force a refresh.

 

But my response has put too much emphesis on the host page. Putting caching rules in place for the *.cache.* and *.nocache.* fixes a lot of the RPC problems. 

 

I could be wrong but the old documentation of GWT used to explain that but the docs on gwtproject.org does not make that very clear or it is hidden well.

 

I would expect that information to be somewhere in a topic on how to deploy GWT Applications but I can find it there.

 

David

On Wed, Nov 13, 2013 at 1:33 PM, Jens <jens.nehlmeier@gmail.com> wrote:

One thing people tend to overlook is (besides the *.cache.* and *.nocache.* files) is that the host HTML page should disable caching.

Why? If its not a dynamic host page it always has the same content. We always cached it before moving to a dynamic host page without any issues.

-- J. 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.