3 ms·
Some of the ideas are already present in Magnet links (http://en.wikipedia.org/wiki/Magnet_URI_scheme http://en.wikipedia.org/wiki/Magnet_URI_scheme).
by ivoras 12y ago
Some of the ideas are already present in Magnet links (http://en.wikipedia.org/wiki/Magnet_URI_scheme http://en.wikipedia.org/wiki/Magnet_URI_scheme).
- fit2rule 12y ago.. and in ipfs too, which has a working implementation: https://github.com/jbenet/ipfs https://github.com/jbenet/ipfs
- snw 12y agothere is also RFC 6920 "Naming Things with Hashes" https://tools.ietf.org/html/rfc6920 https://tools.ietf.org/html/rfc6920
- mmahemoff 12y agoSimilar proposal for script tags http://lists.w3.org/Archives/Public/public-webappsec/2013Feb/0052.html http://lists.w3.org/Archives/Public/public-webappsec/2013Feb... This would avoid the inefficient situation we have at present, where the same jQuery script is fragmented across dozens of CDNs, causing a new request each time even when previous instances are already cached by the browser.
- anon4 12y agoI would love to see maven in the browser. Have each webapp serve a pom.xml listing the libs it uses along with exact versions and be done with this hell. The browser then checks if the lib is installed, if not, it goes through the user-specified maven repositories, then through the default ones and then through the webapp-specific ones searching for the artefact. Problem solved.
- LunaSea 12y agoThe problem is not that simple. Most webapps are compiled and minimised using systems like Closure Compiler, Uglify and R.js (for AMD apps). You almost never point directly to a dependency as a standalone file. Doing so would mean 15-30 requests per webapp and since browsers only accepts 5-6 parallel requests, it would slow down the page considerably.