I understand that. assuming you are calling the module.nocache.js the
"bootstrap" code.

my last question is HOW to make it not cacheable. I know about using
meta tag to mark a page uncacheable, but how do you make one .js
uncacheable?



On Jul 21, 6:48 am, Stefan Bachert <[email protected]> wrote:
> Hi,
>
> the bootstrap code should never be cached.
>
> Assume you are deploying a new version.
> The bootstrap code refers the browser/locale specific JS using an own
> strong name.
> If you cache the bootstrap file, it may happen that old bootstrap code
> refers to old strong named file
> which are no more existing.
>
> Stefan Bachert
> http::/gwtworld.de
>
> due to recent cases, I am sorry, I won't do free personal support.
> inquiries for professional GWT support are welcome.
>
> On 20 Jul., 23:13, bhomass <[email protected]> wrote:
>
> > I found a number of conflicting comments concerning this. And, even if
> > they are in sync, I have questions on how to set cache control.
>
> > 1. you stated - *Never Cache* - The bootstrap <module-
> > name>.nocache.js, and your host html/jsp page falls under this
> > category. The browser should never cache.  but the first reference
> > above says
> > (2) Changing occasionally (public / equal for all users)
> > Examples: index.html, mymodule.nocache.js
>
> > which sounds like you should cache for short time.
>
> > I am unsure how I would set the cache control for the
> > module.nocache.js. The js file is cotained in the app.hmtl. do I set
> > <meta http-equiv="Cache-Control" content="no-store"> in the header of
> > that page?
>
> > should I use no-store or no-cache?
>
> > 2. you stated - *Cache for sometime* - Every other file falls under
> > this category. In
> >    general, you should use ClientBundle so that files don't end in
> > this
> >    category. GWT generated js/html files will never come under this
> > category.
> >    You can choose to set an expires header ranging from a few hours to
> > a few
> >    days, depending on how frequently you change your code.
>
> > I can be sure whether you are saying to use client bundle so that
> > nothing ever get cached for sometime. if so, why do you also specify
> > "set an expires header ranging from a few hours to a few  days"?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
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.

Reply via email to