- From: Karl Dubost <karld@opera.com>
- Date: Tue, 31 May 2011 06:51:43 -0400
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: public-html@w3.org
Cf Content negotiation of images quality based on HTTP [1] Le 31 mai 2011 à 06:23, Henri Sivonen a écrit : > There's an expired ID for that: > http://tools.ietf.org/html/draft-mutz-http-attributes-01 Some mobile devices are currently using CC/PP [2][3], but I have no idea how widely it is used and it might be less obvious than HTTP headers. There is a trade-off. The issue is to find a mechanism in which the information is on the device side to be trusted. (hear go away with user agent sniffing: #sniffkill) From the Mutz draft. UA-pix-x= <n> UA-pix-y= <m> The display size of the client's device is transmitted in total horizontal <n> and vertical <m> pixel number, for example: UA-pix- x=1024, UA-pix-y=768. The intent is to present and allow the selection of the resource variants best suited to a client's device. The draft has a reference to "Transparent Content Negotiation in HTTP" 6.1 Feature tags [4] RFC2295 [1]: http://www.w3.org/mid/5739036C-D7F2-4142-A3EB-33653AFEB038@charlvn.com [2]: http://www.w3.org/TR/CCPP-struct-vocab/ [3]: http://jcp.org/en/jsr/detail?id=188 [4]: http://tools.ietf.org/html/rfc2295#section-6.1 -- Karl Dubost - http://dev.opera.com/ Developer Relations & Tools, Opera Software
Received on Tuesday, 31 May 2011 10:52:21 UTC