[Bug 11402] One problem of todays JavaScript libraries is, that the client has to download the same library over and over again, while visiting multiple sites. One could use services like Google Libraries API for a central location, but that introduces new points of

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11402

--- Comment #5 from Tab Atkins Jr. <jackalmage@gmail.com> 2010-11-30 16:57:43 UTC ---
(In reply to comment #4)
> 1) The browser supports the hash attribute
> 1 1) The browser supports the requested hash algorithm:
> 1 1 1) The library is already cached (Hash matches) -> Use the cached file
> 1 1 2) The library is not cached -> Download the hash file and check the hash
> 1 1 2 1) The downloaded file matches the hash -> Use the downloaded file
> 1 1 2 2) The downloaded file doesn't match the hash -> Discard the downloaded
> file, raise an JS exception
> 1 2) The browser doesn't support the requested hash algorithm -> Download and
> use the specified file
> 2) The brower doesn't support the hash attribute -> Download and use the
> specified file
> 
> 1 1 2 2) Would make the error easier to track.

(1 1 1) is the weak point here, and you haven't fixed it.  If they have a
cached version and they see an un-updated hash that matches the cached version,
they'll continue to get the cached version, not the newly updated one.

And, like Aryeh said, if the user clears their cache but then visits another
page using the same older version of the library, they'll re-cache it and hit
the same problem *again*.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 30 November 2010 16:57:45 UTC