- From: Dave J Woolley <david.woolley@bts.co.uk>
- Date: Wed, 6 Dec 2000 19:05:10 -0000
- To: www-html@w3.org
> From: Philip TAYLOR [SMTP:P.Taylor@Rhbnc.Ac.Uk] > > was explicitly for the case where there are multiple images > to be cached; in this way, there is a single <LINK> to a single > HTML page with multiple <IMG> tags, one for each image to be > [DJW:] Indirection would introduce extra round trip delays and complicate HTTP pipelining. I also feel that there is no reason to have a set of mock images, even if you go indirect; one could use LINK on the indirect page. Pipelining is already quite messy here, because you don't want to start requesting the images until the rest of the page loads, even though they appear first, and you want to pre-empt fetches if the user mouse-overs out of boredom, whilst waiting for the base versions of all the iamges to load. [DJW:] Note that nothing here should be taken as encouragement for implementing buttons as images, or for animating them; I like neither, I'm just trying to consider, from a aminly academic point of view, the most appropriate mapping of the function suggested onto HTML. -- --------------------------- DISCLAIMER --------------------------------- Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of BTS.
Received on Wednesday, 6 December 2000 14:05:21 UTC