Re: [sXBL] Various issues in the sXBL draft -- section 1

On Mon, 28 Mar 2005, Boris Zbarsky wrote:
> 
> Given any "starting" URI, an implentation has to perform the following 
> steps, as I see it:
> 
> 1)  Determine what "resolved" URI this "starting" URI will resolve to after
> all redirects.
> 2)  Look for this "resolved" URI in its "loaded XBL stuff" cache (probably
> need to include "loading XBL stuff" as well, which is a separate issue).
> 3)  If step 2 doesn't find anything, fetch the data for the URI, parse it,
> etc.
> 
> The problem I'm having is with step 1.  If there is no data, or only 
> expired data in the HTTP cache for the "starting" URI, then the 
> implementation has to do an HTTP GET on the "starting" URI to determing 
> the "resolved" URI for step 2. Per the text of the specification, this 
> should happen even if the "starting" URI is already in the cache we 
> access in step 2, since it could now result in a redirect.

Ah, I see where you are coming from. Yes, indeed, if the author has set 
no-cache headers, and the UA is honouring these headers even in the 
course of a single top-level-document load, then every mention will cause 
a hit to the server.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'