3 ms·
Here's some info about including image data as part of the URI: http://en.wikipedia.org/wiki/Data_URI_scheme http://en.wikipedia.org/wiki/Data_URI_scheme. Assu
by Barnabas 17y ago
Here's some info about including image data as part of the URI: http://en.wikipedia.org/wiki/Data_URI_scheme http://en.wikipedia.org/wiki/Data_URI_scheme.
Assuming the HTML is compressed, wouldn't this also achieve the same "poor-man's pipelining" result, as in less server connections? It seems to have broader browser support than the JAR thing.
Edit: I found this too... the MHTML method linked in this article is also interesting: http://danielmclaren.net/2008/03/embedding-base64-image-data-into-a-webpage http://danielmclaren.net/2008/03/embedding-base64-image-data...
- tedunangst 17y agoData uri's can't be cached, so they can only help latency of a cold page load, but they make every page after that slower. (if you put the data uri in your html instead of the css)
- derefr 17y agoYou could also put the Data URIs into a javascript file that plugs them into the document/css/whereever once it's loaded. The script would cache.