W3C home > Mailing lists > Public > public-html@w3.org > August 2013

Re: [Feature Proposal] New attributes "library" and "version" on script tags

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Sun, 11 Aug 2013 08:07:33 +0100
Message-ID: <52073835.9050705@splintered.co.uk>
To: public-html@w3.org
On 11/08/2013 07:38, Andrew Herrington wrote:
> Could this also be used with CSS (twitter bootstrap) and web component imports (twitter / Facebook feeds)?

And bitmap images, SVG files, anything really?

On first reading, there are many aspects I'm personally not a fan of 
(browsers shipping with JS libraries pre-seeded, and the emphasis on 
just JS), but as a more generalised principle, I could imagine something 
along the lines of:

- no pre-seeding
- every asset downloaded and cached by the browser gets some form of 
hash/checksum/digital fingerprint (leaving the discussion of how to do 
this effectively without clashes aside for a minute)
- as part of the request to the server, the browser also receives a 
hash/checksum for the file being sent as part of the initial connection 
negotiation and/or head request
- if the browser thinks that a file that is about to be downloaded is 
already present in its own cache (hash/checksum matches, expire headers 
all ok, etc), it uses its cached version rather than carry on with 
downloading (regardless of origin?)

P
-- 
Patrick H. Lauke
______________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]

www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com | http://flickr.com/photos/redux/
______________________________________________________________
twitter: @patrick_h_lauke | skype: patrick_h_lauke
______________________________________________________________
Received on Sunday, 11 August 2013 07:07:55 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:34 UTC