W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2020

Re: New Version Notification for draft-nottingham-bikeshed-length-00.txt

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 19 Mar 2020 16:25:03 +0000
To: Willy Tarreau <w@1wt.eu>
cc: Cory Benfield <cory@lukasa.co.uk>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <17396.1584635103@critter.freebsd.dk>
In message <20200319161130.GA19209@1wt.eu>, Willy Tarreau writes:
>On Thu, Mar 19, 2020 at 03:53:32PM +0000, Poul-Henning Kamp wrote:

>> We could make it explictly fuzzy, by definting it as kilobytes rounded down ?
>I think it's an excellent idea, which even goes in the direction of
>reducing the on-wire bytes. And given todays connections speeds, if we
>use it only for progress bars it could even represent megabytes rounded
>to the nearest. Less than 0.5 will usually not take more than a few
>seconds and not deserve showing an accurate progress bar.

I thought about that, but I know of applications where traffic is sorted
in "small", "medium" and "huge", where "small" is significantly less than
a megabyte, so I think the units should in the kilobytes rather than
megabytes range.  Just to throw a number out there:  Smaller than 32k.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 19 March 2020 16:25:19 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 19 March 2020 16:25:19 UTC