Remember if using crome with the inspector open, holding down the
reload button gives a option to clear cache/hard reload.
VERY usefull, yet hidden feature.
On Dec 21, 4:54 pm, Thomas Broyer t.bro...@gmail.com wrote:
On Friday, December 21, 2012 12:03:30 PM UTC+1, Marco wrote:
http://seewah.blogspot.de/2009/02/gwt-tips-2-nocachejs-getting-cached-in.html
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/u2JGxvMGRgwJ.
To
On Friday, December 21, 2012 12:03:30 PM UTC+1, Marco wrote:
http://seewah.blogspot.de/2009/02/gwt-tips-2-nocachejs-getting-cached-in.html
See also
https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDebugging#perfect_caching
(which
is also linked from
Is this really i am facing same issues as described below
1. hosted GWT application in IIS.
2. browse the application IE.
3. modified the application.
4. Now hosting it again on IIS in same directory with same name n all.
5. IE is showing old version only until I explicitly clears the history
If that works then it sounds like you don't have caching set up
correctly for the *.nocache.js files. The browser shouldn't be
caching these files at all, to enforce that you'll have to send the
correct response header (Cache-Control: no-cache, no-store) when
handling the request for those
Hi matthew,
Thats a very good approach I like that. Also it doesn't mean the user
has to change the URL they visit and everything for them will just
work! The developers know the difference.
Good approach!
On Nov 1, 5:47 am, mat [EMAIL PROTECTED] wrote:
Hi,
What I usually do is append a
This is how it *should* work, out of the box. Do you have a specific
counterexample?
On Oct 30, 10:31 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
Basically I would like to know how to support the case where we would
like to deploy an updated application and want changes to be
Hi imran,
We have experienced the same problems as you describe in which the
user has to shift reload their browser!
As our app is a J2EE app with JSP's we aim to try and solve this with
the JSP no Cache directives?
eggsy
On Oct 31, 12:15 pm, walden [EMAIL PROTECTED] wrote:
This is how it
I have similar problem to what Eggsy has described, whereby in order
to view the most recent changes it becomes necessary to clear the
browser cache. Unfortunately, apart from a couple of minor JSP pages,
most of our system is built entirely using GWT.
Is there some approach within the GWT
Hi,
What I usually do is append a random querystring (for each new
version) to the javascript include on the HTML page.
e.g
script language=javascript src=http://www.google.com/MyScript.js?
version=20081101/script
The browser sees this as a different URL to http://www.google.com/
MyScript.js.
10 matches
Mail list logo
