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

Re: New document on "Simple hit-metering for HTTP"

From: Jeffrey Mogul <mogul@pa.dec.com>
Date: Wed, 14 Aug 96 17:08:42 MDT
Message-Id: <9608150008.AA17384@acetes.pa.dec.com>
To: Koen Holtman <koen@win.tue.nl>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1350
    It would be better to [...]
    instead add stuff to make being cooperative less costly (e.g. a method
    to piggy-back hit count reports for other URLs on a request you have to
    send anyway).

I don't think we need to add very much at all for this.  Remember
that the count report can be sent over the same persistent connection
as other operations being sent to the server.  A typical count report
would be
	HEAD /foo.html HTTP/1.1
	Host: www.w3.org
	Cache-control: use-count=37
if no Vary was sent, or something like
	HEAD /foo.html HTTP/1.1
	Host: www.w3.org
	User-agent: SuperBrowser 1.1
	Cache-control: use-count=37
otherwise.  These are short enough that you can probably send 4 or 5
of them without increasing the number of TCP packets (although the
length of certain packets would increase) in the typical case.

Clearly, some sort of header-abbreviation or tokenization would
reduce the overhead even more, although you would have to at least
transmit the URL+host for each report.  It looks like the average length
of possibly-cachable URLs in our proxy logs is about 48 bytes
(including host names).

Received on Wednesday, 14 August 1996 17:19:11 UTC

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