W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2012

Re: RFC: draft-brown-device-stock-ua-00.txt

From: Ludin, Stephen <sludin@akamai.com>
Date: Wed, 14 Nov 2012 18:03:51 -0600
To: Eitan Adler <lists@eitanadler.com>
CC: Ilya Grigorik <ilya@igvita.com>, John Kemp <john@jkemp.net>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <CCC96FED.6A3A9%sludin@akamai.com>
I am not certain I understand the question, but I'll answer with where the
'situational' part could come in.  The two simplest are:

1) Origin outputs device specific content and uses the intermediary simply
to accelerate and/or cache
2) Origin serve generic content and the intermediary performs the
appropriate adaptation

I the latter example, the origin dose not necessarily need to know the
device details and removing or changing the header may be appropriate.  In
the former the header is less important to the intermediary though they
still may need to for caching the content appropriately of so desired by
the origin.

-stephen

On 11/13/12 7:30 PM, "Eitan Adler" <lists@eitanadler.com> wrote:

>On 13 November 2012 17:26, Ludin, Stephen <sludin@akamai.com> wrote:
>> As an intermediary/surrogate, this makes a lot of sense.  I can see the
>> specific behavior required being very situational.
>
>When might I ask, would Akamai want to take action based on a browser
>the user not using and may not even be installed?
>
>
>-- 
>Eitan Adler
Received on Thursday, 15 November 2012 00:04:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 November 2012 00:04:32 GMT