dean blackketter wrote:
Funny you should mention this...
By caching on the server, do you mean writing resized images into the library (or some sort of img-cache dir)? Seems like you could do this once on scan, store the path/filename in the db and be done with it. Big gains for browsing, and for all but the first scanner pass.
Another gain in the browsers will be in page scrolling. From what I can tell, the browsers seem to call their resize code in the renderer as the images need to be flowed into the layout. So when you scroll and hit new images, they have to be resized on the fly, which is performance intensive, and this produces glitchy scroll behavior. And the ones that fall off the screen seem to be thrown away and recalc'd when you scroll back. Not good.
Anyway, serving correctly sized-for-display images is just better. And don't forget to update the HTML markup to include img tag height and width attributes. This hints the layout engine and allows for quicker paints.
Yip! --rt _______________________________________________ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
