[Cosmo-dev] Caching Issues Followup

[Travis Vachon]

>
>> There are other bugs which are blockers  on everyone's plate and this
>> one has proven to be quite a time-suck for Travis (and myself to a
>> lesser extent)
>
> i understand that this bug is hard to chase down, and for that reason
> other blockers should have priority over it, but once they're done, we
> should try again.
+1
>
>> If we had a developer focus on pretty much just this for a while I'm
>> sure we could solve it, but the issue is...what is "a while"? Do we
>> let this hold up preview?
>
> +0. i don't believe we should release without fixing the bug, but as i
> probably can't effectively contribute to finding the problem, i can't
> take a firmer stance.
>

+/-0 (does that exist?) with the caveat that I'd feel stronger (+1)  
if we can determine that fixing this bug would provide significant  
end user experience (that is, performance) enhancements.

Right now my best idea for a way forward is documented on bug 9715.  
The short version is that I've determined we most likely do not see  
this behavior if we explicitly remember and set Etag/If-None-Match  
and Last-Modified/If-Modified-Since headers. The one caveat is that  
we see slightly different XHR behavior that I think would require at  
least a days worth of refactoring, and possibly more if Safari/IE  
behavior is not the same as Firefox behavior in this regard.

The other possible way forward would be to start talking to the  
Firefox developers. As best as I can figure this is in reality a  
Firefox bug. However, given our current lack of reliable reproduction  
steps I can only assume this would take long enough as to be  
definitely out of scope for 0.7.

-Travis