Re: XmlHttpRequest not loading latest version of xml
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.lang.javascript archive

Re: XmlHttpRequest not loading latest version of xml

From: Matt Silberstein <RemoveThisPrefixmatts2nospam@ix.netcom.com>
Date: Wed Nov 30 2005 - 19:16:35 CET

On Sat, 26 Nov 2005 19:27:51 GMT, in comp.lang.javascript ,
jim@jibbering.com (Jim Ley) in
<4388b659.210154225@news.individual.net> wrote:

>On Sat, 26 Nov 2005 20:18:09 +0100, Thomas 'PointedEars' Lahn
><PointedEars@web.de> wrote:
>
>
>>Tell the server to identify its responses through headers. This way,
>>any standards compliant non-broken non-misconfigured user agent (client)
>>will not use its local cache and any intermediary proxy server will not
>>use its cache if the cached resource says so.
>
>No, there is no MUST requirement on the client that proxies or the
>client obey them, so it's not simply a broken issue. Even if it was,
>then changing the URL _aswell_ would do nothing to change the
>behaviour in correct clients, and would also support broken ones.
>
>Changing the URL is very good advice, stop advising against it.

One issue that concerns me is that it is the server that knows if the
data is old, not the client. Making client side determinations is
non-optimal.

-- 
Matt Silberstein
Do something today about the Darfur Genocide
http://www.beawitness.org
http://www.darfurgenocide.org
http://www.savedarfur.org
"Darfur: A Genocide We can Stop" 
Received on Sat Dec 3 04:33:46 2005