- From: Mark Baker <mark@coactus.com>
- Date: Wed, 1 Apr 2009 20:08:23 -0400
- To: Adam Barth <w3c@adambarth.com>
- Cc: Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, HTTP Working Group <ietf-http-wg@w3.org>
On Wed, Apr 1, 2009 at 7:48 PM, Adam Barth <w3c@adambarth.com> wrote: > On Wed, Apr 1, 2009 at 4:45 PM, Mark Baker <mark@coactus.com> wrote: >> Right. The information you're talking about is irrelevant to most >> non-browser HTTP agents and so doesn't belong in the HTTP >> specification. > > It's relevant to any HTTP user agent that wishes to interoperate with > existing Web content. For example, Imageshop (described earlier in > this thread) is not a browser but is interested in knowing when its > users expect an HTTP response to be treated as an image. Yes, of course. I'm trying to emphasize to you that the Web is a lot larger than just those clients and servers exchanging HTML, Javascript, and JPGs. If that weren't the case, I would agree with you that HTTP should be updated. Mark.
Received on Thursday, 2 April 2009 00:09:25 UTC