Difference between revisions of "Headlights2013/3rdPartyLibraryCaching"

From W3C Wiki
Jump to: navigation, search
(One Hundred Word Description of the Idea)
(Replaced content with "Moved to Team wiki")
 
Line 1: Line 1:
===Name of idea===
+
Moved to Team wiki
 
+
Create mechanism for standard caching of 3rd party JavaScript/other libraries
+
 
+
===Submitter name===
+
 
+
Chris Mills, compiled from useful discussion with Liam Quin, Phil Archer, and others. See [https://lists.w3.org/Archives/Team/w3t/2012Nov/0200.html thread starting here].
+
 
+
===Classification===
+
 
+
This idea is A specific technology area that requires new standardization (e.g. structured vocabularies, privacy, REST)
+
 
+
===One Hundred Word Description of the Idea===
+
 
+
3rd party JavaScript libraries such as jQuery are ubiquitous these days, and the majority of web developers use them every day as a matter of course, including them in standard development templates even then they are being used for trivial tasks or not at all. This leads to a more inefficient web, with unnecessary extra performance hits that are particularly costly to mobile devices/lowered powered devices/devices using slow network connections. To improve this situation, the W3C should define a standard mechanism for including all these libraries in the browser (or to include equivalent API support in the browser) so they don't have to be downloaded each time, including checking to see if the browser needs to update the cached versions of the libraries it has stored, etc.
+
 
+
===Benefit(s) to W3C===
+
 
+
More efficient running of open web applications, better user experience for emerging markets.
+
 
+
===Which of our stakeholders would be the most enthusiastic in supporting===
+
 
+
Browser/OS/hardware vendors, especially those involved mobile/device and based in less developed countries.
+

Latest revision as of 16:02, 5 December 2012

Moved to Team wiki