On Thu, Sep 17, 2009 at 4:08 PM, Maciej Stachowiak <[email protected]> wrote:
> > On Sep 17, 2009, at 2:16 PM, John Abd-El-Malek wrote: > > >> >> I think the image trick is more attractive than <a ping> because it's >> easier for web developers to use. But I'm not convinced it's the cleanest >> method we can come up with. If we are expecting web developers to change, >> then I'd prefer something more explicit link asyncPing(url). The benefit is >> that it doesn't tie up connection limits like image loading would, and hence >> shouldn't impact the navigated page's loading. The UA is then free to pick >> the best time to do the ping, i.e. when network activity has died down. >> >> > With the Image trick, web developers don't have to change, other than to > get rid of the busy loop. I wouldn't be too averse to also adding an > explicit ping API, but it seems to me it's possible to do many of the > optimizations you describe for the Image-in-unload trick. > Good points. These were my biggest sticking point with the image trick, now that I'm not concerned about them anymore, I really appreciate the compatibility with IE that this gives. > > - Maciej > >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
