News for hackers. Stuff that matters.
Re:IPhone Web App Performance Tip - Use Inline Images by tlrobinson on Wednesday August 27, 2008 @02:24AM (#287823)
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.

Re:IPhone Web App Performance Tip - Use Inline Images by pmjordan on Thursday August 28, 2008 @10:19AM (#289130)
The 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.
Re:IPhone Web App Performance Tip - Use Inline Images by tlrobinson on Friday August 29, 2008 @08:27PM (#290586)
Good 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.
Re:IPhone Web App Performance Tip - Use Inline Images by thamer on Wednesday August 27, 2008 @04:43AM (#287868)
Also, 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?