On 2012-12-30, at 10:07 PM, Sherif Ramadan <[email protected]> wrote:
> Sorry, that was poorly worded. I didn't mean to suggest that the each data > URI generates a transfer over TCP. What I'm saying is that there is a > caching disadvantage here since the initial JSON request itself can't be > cached (the one coming from http://prototype.php.net/images/elephpants.php). The JSON request could be cached. It is designed to return a random collection of images, so you would have to be willing to give up some randomness, but there is no reason it couldn't be cached. > For each of these data URIs the browser will consider it as a request even > though nothing is actually transferred over HTTP from the data URI, > obviously, but that's still not great. The reason being each data URI > requires encoding/parsing on every single request (that's extra time to > render the page that could be avoided). Have you measured this? I don't think there is any significant overhead to data URIs. -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
