It appears that when using Ajax to render html content, Safari seems to forget that it has already cached images, and instead, re-loads the same images.
This is not the case when the images (say button images) are specified in a css. In this case, the Ajax loaded images work fine (meaning Safari does not attempt to get the same image from the server more than once). However, I have an application that renders cover art for an album collection. To scroll through the collection, I use Ajax to tell the server to render the next page of albums. The cover art loads. When I press a button to use Ajax to render the previous page (presumably safari has already cached those images), I notice that Safari re-loads the images from the server and not from the browser cache. BTW - I'm using the Desktop Safari Web Inspector under the Develop menu item to view this effect. I don't necessarily mind the back and forth to the server to retrieve images (using wifi), however, I notice that Safari on the desktop is continually increasing in Real memory consumption as the images are constantly re-downloaded. Could this also be happening ion the iPhone/ Touch? Is this a known issue? Any workarounds? I've seen several discussions about this issue residing in Internet Explorer. Any help or enlightenment is appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
