- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 27 May 2009 09:32:17 +0200
- To: Werner Donné <werner.donne@re.be>
- CC: WebDAV <w3c-dist-auth@w3.org>
Werner Donné wrote: > Hi, > > I would not limit preview-sets to images. Any type of document can have a > preview thumbnail (cfr. Coverflow on Mac OS X). Yes, that was the intention. Another use case are short, low-quality excerpts from audio files. > When retrieving preview-set in expand-property, into what the URLs in > preview-set would expand? That would be server-defined. In theory, it wouldn't need to be WebDAV resources at all. > There should be a property to represent an embedded form of a thumbnail, > i.e. > one that also contains an element with the base64-encoded binary stream of > the thumbnail. This way the contents of a folder, thumbnails included, > could > be retrieved with a single round-trip, which is much more efficient on the > server-side. Such a property would be available directly in the PROPFIND > method. > ... In theory that can be done using the "data" uri scheme as well. The tricky question here is who's role is to decide when inlining is better; the client or the server? (the latter does have more information about the size). Also, inlining has the drawback of defeating caching. BR, Julian
Received on Wednesday, 27 May 2009 07:32:57 UTC