Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XMLHTTPRequest caching problem

From: Adrian Herscu <bmf1972@-------.--->
To: NULL
Date: 7/3/2005 9:50:00 PM

Neil Smith [MVP Digital Media] wrote:
> On Sat, 02 Jul 2005 14:28:43 +0300, Adrian Herscu
> <bmf1972@a...> wrote:
> 
> 
>>Hi Neil,
> 
> 
>>This solution is worse than the previous one since it requires the 
>>installation of some server-side software (the PHP script requires a 
>>special scripting engine).
> 
> 
> Ah, I rather intended you would recognise what that script did, and
> implement it in your language or server of choice ;-) 
> 
> IIS ISAPI and Apache can be arranged to generate those headers when a
> document is requested for a particular virtual directory, I just
> didn't know if you generated the XML dynamically (as you implied)
> using a scripting language such as .NET, or if it was a static file
> which you updated out-of-band.

Still, this requires fiddling with the server. And the most important, 
no caching will be done.
I said from the beginning that those are "static" files which are 
manually updated from time to time.

Is this a bug of MS-IE/MS-XML or not?

> 
> CHeers -o Neil


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent