W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2007

Re: Accept- & Content-Resolution headers proposal

From: Mike Dierken <dierken@gmail.com>
Date: Thu, 7 Jun 2007 09:09:07 -0700
Message-ID: <7cd8e0930706070909oaede6b9j2f15035c1c98aee@mail.gmail.com>
To: "Nicholas Shanks" <contact@nickshanks.com>
Cc: ietf-http-wg@w3.org, "WebKit Development" <webkit-dev@lists.webkit.org>

Where did the "/style/default" URI come from to begin with?
If from a document of some sort, could that document describe the
choices right there with distinct URI for each supported resolution?
Adding that description of resolution specific resources only requires
updating the definition of those document formats, rather than
updating a protocol that is device and document format independent.



>
> The client (a laptop, say) requests -
>
> GET /style/default HTTP/1.2
> Host: example.com
> Accept-Content: text/css, text/dsssl, text/xsl
> Accept-Resolution: 116.66 dpi
>
Received on Thursday, 7 June 2007 16:09:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:10 GMT