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: Willy Tarreau <w@1wt.eu>
Date: Thu, 19 Mar 2020 17:28:51 +0100
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Cory Benfield <cory@lukasa.co.uk>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20200319162851.GB19209@1wt.eu>
On Thu, Mar 19, 2020 at 04:25:03PM +0000, Poul-Henning Kamp wrote:
> --------
> 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.

I'm fine with this anyway.

Willy
Received on Thursday, 19 March 2020 16:29:09 UTC

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