On Saturday, July 11, 2015 at 4:28:30 PM UTC+2, gocelticsp...@gmail.com
wrote:
>
> A customer of our GWT 2.6.1 based product that runs on Tomcat has
> requested to not have to cache our application every time we deploy a new
> version. I have read many posts about various methods to prevent this
> from happening and many are dated over two years ago. One of the main
> issues I see is that the proposed solutions will slow down the startup of
> the application and most seem to be "in theory" this will work. What is the
> best solution for this at this point and what has worked for other apps?
> One of the possible solutions we found would be to add the following in
> main.jsp:
>
> <script
> src="${pageContext.request.contextPath}/VMGui/VMGui.nocache.js?version=${new
> Date().getTime()}"></script>
>
Have you tried just setting Cache-Control headers in the HTTP response?
You can use https://github.com/realityforge/gwt-cache-filter or Tomcat's
ExpiresFilter
<https://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#Expires_Filter>
See
http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching
for the recommended values.
--
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+unsubscr...@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/d/optout.
