Technically it isn't GWT but rather your browser that caches the
response.
There are a couple of ways to get around the caching done by your
browser.
A client side (GWT) solution would be to add a "cache buster" to the
servlet url as a query parameter. This could be something like a
filename, or a time stamp depending upon what is appropriate for the
situation.
A server side solution would be to configure your web server to add
cache-control headers to the response generated by the server. How you
would do this really depends upon your server and there is no single
"do it this way" solution for all cases.
One other possibility is to use HTTPS as browsers automatically DO NOT
cache anything over HTTPS.
-jason
On Oct 1, 2008, at 10:08 AM, ArunDhaJ wrote:
>
> Hi All,
> I'm calling a servlet using asyncGet method of HTTPRequest
>
> HTTPRequest.asyncGet(url,new ResponseTextHandler() {
> public void onCompletion(String responseText) {
> RenderXML(responseText);
> }
> });
>
> The servlet is called first time only, the later request doesnt call
> the servlet. Is GWT caching the response? If so, how to clear it?
>
> Thanks in Advance !
>
>
> -ArunDhaJ
> >
--~--~---------~--~----~------------~-------~--~----~
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-Toolkit@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
