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

Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs

From: Jan Algermissen <jan.algermissen@nordsc.com>
Date: Fri, 16 Dec 2011 01:44:37 +0100
Message-Id: <DF2AD52A-23EB-4212-82BC-3BD65E2CE014@nordsc.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Hi,

On Dec 16, 2011, at 1:04 AM, David Morris wrote:

> The whole User Agent vs. Client
> distinction is not useful in helping folks understand the protocol
> and requirements for robust interoperation.

I think it is because it helps to differentiate connector (client) from component (user agent). Much of the HTTP spec deals with stuff that regards correct connector implementation, but, e.g. headers such as User-Agent or Accept apply to the user agent and its capabilities.

I think that the HTTP spec can contribute to correct use of HTTP by emphasizing that a user agent is a software component that takes actions on behalf of a user and is not just constructing HTTP requests and receiving responses (that is what the client does).

Jan


[1] Such as 'GETing all resources referenced by HTML <img>-elements and embedding them in the rendered page' or 'GET article details from diverse sites, compare prices and initiate order of cheapest article'
Received on Friday, 16 December 2011 00:45:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:51 GMT