Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-12 Thread Windy Road
Hi, So it appears that there are no plans to implement feature negotiation in Apache at this point in time. I'm willing to look into modifying mod_negotiation to support some level of feature negotiation if someone is willing to implement something on the WebKit side. Anyone interested?

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-11 Thread Windy Road
Hi, Does Apache support Feature negotiation as specified in RFC 2295 (see http://www.ietf.org/rfc/rfc2295 )? If so, is there any documentation related to this (I couldn't find any)? If not, are there any plans to support this portion of the RFC? FYI the back story to this request is from a

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-11 Thread Windy Road
Hi, Are there any plans for Apache to support Feature negotiation as specified in RFC 2295 (see http://www.ietf.org/rfc/rfc2295 )? FYI the back story to this request is from a discussion on the webkit-dev mailing list regarding having images served to a client dependant on its resolution and/or

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-08 Thread Peter Speck
On 07/06/2007, at 22:38, Maciej Stachowiak wrote: The only case that needs to be addressed better IMO is foreground images via img. And that should probably be handled at the HTML or CSS level, not the HTTP level. But the html doesn't know (today) which dpi the display is using. When

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-08 Thread Nicholas Shanks
Hi Peter. I recommend you take a look at what Larry Masinter pointed out. It becomes clear that all of this has already been solved 9 years ago, but because it (apparently) isn't enabled in Apache by default, I and many others never even realised it existed: Content negotiation for HTTP

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-08 Thread Peter Speck
On 08/06/2007, at 13:07, Nicholas Shanks wrote: http://www.ietf.org/rfc/rfc2295 [...] In light of this, I suggest that WebKit developers (including me if I get the time) look into implementing this set of RFCs, and ignore all previous suggestions. It seems we've been in the classic

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-08 Thread Rob Burns
Hi Nicholas and Peter, That is great (though ironic) to hear that this feature's been there all along (at least in the spec and in the server). I wonder if you (Nicholas) could write up or point to some instructions on configuring that in Apache (ideally the exact lines to add to the

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Maciej Stachowiak
On Jun 7, 2007, at 6:27 AM, Nicholas Shanks wrote: It has been mentioned on the Safari WebKit development mailing list that a HTTP header which specified a document's target resolution would be useful to allow clients to negotiate for high-res or low- res artwork and CSS referring to such

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Maciej Stachowiak
On Jun 7, 2007, at 9:00 AM, Nicholas Shanks wrote: Sorry, Accept-Content: text/css, text/dsssl, text/xsl should of course have referred to Accept-Type :-) Actually it should have been Accept:. There is no Accept-Type header. - Maciej ___

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Rob Burns
Macej, I think you misunderstand the proposal. It does take scale factor into account. It also is meant to handle other cases (not just CSS). I do think you're right about the server advertising the possibilities, but that would probably complicate things a lot. In any case its better

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Andre-John Mas
Surely all of this becomes moot if we specify objects in terms of inches, cm or mm, all of which are already supported by css? A browser that interprets these 'absolute' units properly should already know what DPI the current environment is in, or have access to the necessary API to

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Rob Burns
On Jun 7, 2007, at 3:52 PM, Andre-John Mas wrote: Surely all of this becomes moot if we specify objects in terms of inches, cm or mm, all of which are already supported by css? A browser that interprets these 'absolute' units properly should already know what DPI the current environment

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Nicholas Shanks
On 7 Jun 2007, at 23:07, Rob Burns wrote: PS, again my suggestion is for the client to request specific pixel dimensions for the media not the ppi/dpi/cmpi) If the the UA is in an environment with multiple displays or multiple resolution output of any kind it can use that in determining

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Nicholas Shanks
sorry for more spam people :-) a couple of things i don't have time to write about before i go to bed (tis gone 1am here) http code 300 is what i was wanting, not 406 or making up a new one http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.1 the Suggest-Location param