On Sep 3, 3:59 pm, dduck <[email protected]> wrote: > On 3 Sep., 14:37, Thomas Broyer <[email protected]> wrote: > > > On Sep 3, 2:24 pm, dduck <[email protected]> wrote: > > If you want to cache images, you have to have your server send the > > appropriate HTTP headers so the browser itself appropriately uses the > > image from its cache. > > Unfortunately it seems that most browsers are smart enough to cache > images that have been fully transfered, but not smart enough to > consolidate overlapping requests such as this: > > time:0 fetch image1 > time:10 fetch image1 > time:20 Image 1 ready
That's what GWT tries to cope with... only with IE6 (see com.google.gwt.dom.client.ImageSrcIE6). There must be a reason for segregating IE6 (there's even a test so that IE7, which uses the same permutation code, doesn't use this code path); browsers are generally smart enough, even in these cases. Something to do with the image URLs, maybe? (containing query-strings? that'd be Too Bad™ on part of browsers) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
