W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1997


From: Scott Lawrence <lawrence@agranat.com>
Date: Sun, 10 Aug 1997 09:58:47 -0400
Message-Id: <199708101358.JAA05690@devnix.agranat.com>
To: HTTP Working Group <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4137

JF> The bottom line, though, is that there are three pieces of version
JF> information related to an HTTP transaction: 1) the capability version
JF> of the sender, 2) the entity version of the transaction, and, for
JF> requests, 3) the requested version of the response.

  As David W. Morris points out, I misquoted in my response; to

  There is no such thing as the 'entity version of the transaction'.
  Indeed, to make the statement even more concise, there is no such
  thing as the 'entity version'.

  The requestor has a version, and sends it (which may, at the
  requestors option for whatever reason, be less than the highest
  version it could use); the responder has a version and sends it, but
  the response itself must always be valid according to the rules of
  version sent by the requestor.  What could be simpler?

Scott Lawrence           EmWeb Embedded Server       <lawrence@agranat.com>
Agranat Systems, Inc.        Engineering            http://www.agranat.com/
Received on Sunday, 10 August 1997 06:59:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:20 UTC