Archive of UserLand's first discussion group, started October 5, 1998.

Quicker image rendering

Author:Tommy Sundström
Posted:5/19/1999; 2:55:08 PM
Topic:Quicker image rendering
Msg #:6478
Prev/Next:6477 / 6479

When serving a page dynamicly (from a rather slow server) it seams that I get the html-part quite quickly, but that the images rendered from #images are much slower.

This makes me wounder if one factor could be that Frontier has to "open" every image to read the height and width of it?

This seams to be values that could be cached.

So I have a suggestion:

Reform the #images table the same way #glossary was reformed. Introduce a new format where an image is a table. One cell is the binary image data. Other cells are used to cache the height and width after the first time they are sampled. As in #glossary the old format with one binary cell/image is still suported, for backwards compability.

This could have other advantages also. For example, I would most of the time prefer to store the alt-text together with the image, instead of in the html-code. Same thing with lowsrc and probably some other attributes. (And the rule could be that if an attribute is set in imageRef it overrides an attribute in the #image table.)

There are responses to this message:

This page was archived on 6/13/2001; 4:50:18 PM.

© Copyright 1998-2001 UserLand Software, Inc.