W3C home > Mailing lists > Public > public-respimg@w3.org > November 2013

Re: [client-hints] new v1 spec draft and src-N interop

From: Ilya Grigorik <igrigorik@google.com>
Date: Fri, 1 Nov 2013 08:54:49 -0700
Message-ID: <CADXXVKoEYxLAvqqtYLtFpJ2cH-j7wXfa-Nm-MJvZDqfprd+c4Q@mail.gmail.com>
To: "Darrel O'Pry" <darrel.opry@imagescale.co>
Cc: "public-respimg@w3.org" <public-respimg@w3.org>
On Thu, Oct 31, 2013 at 9:04 PM, Darrel O'Pry <darrel.opry@imagescale.co>wrote:

> I was confused from reading the spec about whether each hint was an
> individual HTTP Header. The README.md clarified that for me. I was under
> the impression there was still a Client-Hints: header with multiple values
> inside it for the hints. I like individual headers, they are much more for
> Vary and managing intermediate caches.
>

Yep.


> What would CH-RW be populated with for a non-image request, viewport
> width? Are there usages for these client hints beyond the image use cases?
>

Great question, TBD. We started discussing this in [1] and I broke it out
into a separate issue [2]. If you have any thoughts or suggestions, let me
know (or even better, leave a comment on GH bug :)).

ig

[1] https://github.com/igrigorik/http-client-hints/issues/3 (scroll towards
the end...)
[2] https://github.com/igrigorik/http-client-hints/issues/18
Received on Friday, 1 November 2013 15:55:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:10 UTC