@Andre & Nirmal : Thank you very much for such valuable solution.
I dont have htaccess file as my application is getting deployed on
the google
appengine so how to send headers along with html is a big question mark in
front of me...
i have found one solution for this is that manipulating appenging-web.xml
which has one important parameter
from cache point of view that is
<static-files>
<include path="/**.png" expiration="1d" />
<include path="/**.jpg" expiration="1d" />
<include path="/**.gif" expiration="1d" />
<include path="/**.js" expiration="1d" />
</static-files>
so by using this tag i can make my javascripts,htmls,images cacheable which
could be one solution but as
htaccess provide us direct way to manage html file's headers of our web
application,
i would like to implement something like that.
if anybody has implemented it using appengine then please let me know.
--
Aditya
2010/6/29 André Moraes <andr...@gmail.com>
> All the code generated by GWT (css, javascript, images).
>
> Are cacheable by default, since the name of the resource is generated
> by the hash of the contents (i think it is CRC 32, but not sure).
>
> The best way to cache things is to let your web-server handle this.
>
> Apache, nginx, tomcat have a very good cache mechanism which adds some
> special headers inside the HTTP Response and those headers are
> understood by almost any browser.
>
> You can configure your server to mark all *.cache.* files to be cached
> forever. If you change the code of your app, the GWT will change the
> name of the files and then change what is requested from the server,
> so the old files will not be used and the browser will discard them
> later.
>
> The only caution is to disable the cache for the files *.nocache.*
> because these files will not change and the browser must download them
> every time the user goes to your application. Luckly there are only a
> few files (sometimes can be only one file) that will be non-cacheable.
>
> The solution proposed by Nirmal is the way to go (especially the
> CacheFilter), but check the new docs because the way Css and
> ImageResources are handled changed to a better way in the more new
> version of GWT.
>
> On 29 jun, 09:25, Aditya <007aditya.b...@gmail.com> wrote:
> > hello,
> >
> > I m using GWT on client side which includes lots of code and lots of
> > processing which makes my GWT modules little heavier and
> >
> > Whenever i test it online it loads little slower than it was expected
> > when i searched around the web i found the solution that I can
> >
> > make my static content cacheable i have pure HTML pages i dont know
> > how to make it cacheable.
> >
> > I have included meta tags in my pages but most of the browser doesn't
> > support these meta tags.
> >
> > So what could be done in such situation...?
> >
> > --
> > Aditya
>
> --
> 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...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
--
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...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
