3 ms·
One thing to remember is Base64 encoding is less efficient than the raw binary. Also, all modern web servers and browsers support reusing TCP connections for mu
by tlrobinson 18y ago
One thing to remember is Base64 encoding is less efficient than the raw binary. Also, all modern web servers and browsers support reusing TCP connections for multiple HTTP requests (though there is still the extra latency for each actual request, just not the TCP connection sequence, etc)
I'd be interested to see actual benchmarks, rather than this "trust me, it works" thing.
- thamer 18y agoAlso, doesn't Safari on iPhone cache images? For those with a bandwidth cap, downloading all the images on every page could be quite heavy. Not sure if this is a great idea if navigation involves multiple image-rich pages. Any idea?
- pmjordan 18y agoThe Base64 issue should be relatively minor as long as you're gzip-encoding everything your server sends. (the iPhone supports that, right?) Each base64 byte only has 6 bits of entropy so it'll compress well. I'd be more worried about maintaining efficient caching with this technique.
- tlrobinson 18y agoGood point. I did a quick test with a 190K PNG. Base64 encoded then gzipped it was almost exactly the same size as the original gzipped.