Hi,
caching is controlled by the container. THere is no general way to
configure it.
On Jetty you have to extend web.xml
On Apache you have to configure some .conf or .htaccess
On GAE there is an appconfig
Stefan Bachert
http::/gwtworld.de
Inquiries for professional GWT support are welcome.
I a
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 wrote:
> Hi,
>
> the boo
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 existi
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 .nocache.js, and your host html/jsp page falls under this
category. The browser should never cache. but the first re
>
> I see in repeated cases, where someone's browser displays old app design,
> and clearing browser cache brings up the latest. How can that be?
A few things can go wrong -
1. Browser is caching .nocache.js. If this happens, the browser
will also download the stale *.cache.html files. And
I don't understand something. according to you, none of the generated
js would fall under "cache for sometimes". That means all the js files
except nocache.js would be cached forever. and GWT takes care that new
file names will be generated when this type filed change. By this
logic, there could ne
Nice!
2010/6/26 bhomass
> do you mean to set a limited cache lifetime or to not cache at all?
>
> I do normally want the javascript files to be cached for performance
> purposes.
>
> On Jun 17, 10:02 pm, Sripathi Krishnan
> wrote:
> > No, you can't do that. But if you set appropriate cache he
Its obviously a great idea to cache, and GWT makes it really easy to do
that.
There are in general three buckets of cache settings that you should know
about -
1. *Cache Forever* - Any file that has the extension .cache.xxx falls in
this category. It is safe to set a far-in-the-future expi
do you mean to set a limited cache lifetime or to not cache at all?
I do normally want the javascript files to be cached for performance
purposes.
On Jun 17, 10:02 pm, Sripathi Krishnan
wrote:
> No, you can't do that. But if you set appropriate cache headers, there is
> never a need to delete ol
No, you can't do that. But if you set appropriate cache headers, there is
never a need to delete old files.
--Sri
On 18 June 2010 06:10, bhomass wrote:
> is there any way to programmatically get user browser to delete all
> its cached javascript files in order to push down new ones?
>
> --
> Y
is there any way to programmatically get user browser to delete all
its cached javascript files in order to push down new ones?
--
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-tool...@googleg
11 matches
Mail list logo
