W3C home > Mailing lists > Public > www-style@w3.org > September 2009

Re: Image sprites use cases

From: Pascal Germroth <pascal@germroth.name>
Date: Wed, 02 Sep 2009 01:52:14 +0200
Message-ID: <4A9DB3AE.3060409@germroth.name>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Aryeh Gregor <Simetrical+w3c@gmail.com>, Boris Zbarsky <bzbarsky@mit.edu>, Patrick Garies <pgaries@fastmail.us>, www-style@w3.org
Hello,

> On Tue, Sep 1, 2009 at 6:38 PM, Aryeh Gregor<Simetrical+w3c@gmail.com> wrote:
>> On Tue, Sep 1, 2009 at 7:29 PM, Pascal Germroth<pascal@germroth.name> wrote:
>>> On tool support: It should be relatively easy to write an apache httpd
>>> extension which will create ZIP-files or multipart MIME files on the fly
>>> (cached, of course) off a folder (tree) or the manifest.
>> How would it output the proposed <link> header into the HTML page, and
>> figure out which files need to be in the resulting packed file?  I
>> don't see any possible way this could work without the author manually
>> choosing which files to pack.
> 
> You'd specify a folder that should be sent in this form ("/static/" in
> the example).  The <link> can be sent as a Link: header.

Or you link (maybe also as <link>) to a manifest file which the httpd
processes. Maybe authors want different resource packages for different
pages? I would not go as far and automatically include the links from
the plugin.

The manifest could be a simple list of file names (probably also an
include directive) with wildcards. When requested via HTTP, the server
will not send the manifest, but the resource package, like content
negotiation does. The mime headers/XML manifest could be generated
automatically, using the headers that would be sent if every single file
in the package were requested via HTTP.
Received on Tuesday, 1 September 2009 23:53:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:20 GMT