Re: Live Byte Ranges

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Mon, 28 November 2016 19:57 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E224129A81 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 28 Nov 2016 11:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBId2ZgUzlG7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 28 Nov 2016 11:57:20 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 974A51295F6 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 28 Nov 2016 11:57:20 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1cBRza-0005Dr-Ki for ietf-http-wg-dist@listhub.w3.org; Mon, 28 Nov 2016 19:53:34 +0000
Resent-Date: Mon, 28 Nov 2016 19:53:34 +0000
Resent-Message-Id: <E1cBRza-0005Dr-Ki@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <phk@phk.freebsd.dk>) id 1cBRzP-0005AV-Pv for ietf-http-wg@listhub.w3.org; Mon, 28 Nov 2016 19:53:23 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by titan.w3.org with esmtp (Exim 4.84_2) (envelope-from <phk@phk.freebsd.dk>) id 1cBRzJ-0004Lv-Bb for ietf-http-wg@w3.org; Mon, 28 Nov 2016 19:53:18 +0000
Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id D627A27378; Mon, 28 Nov 2016 19:52:53 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id uASJqq96035075; Mon, 28 Nov 2016 19:52:52 GMT (envelope-from phk@phk.freebsd.dk)
To: Patrick McManus <mcmanus@ducksong.com>
cc: HTTP Working Group <ietf-http-wg@w3.org>
In-reply-to: <CAOdDvNrrLfh0yV4UdBN_HpHNfD024Kufibe3D4ZB1N-SqYVt4g@mail.gmail.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <CAOdDvNrrLfh0yV4UdBN_HpHNfD024Kufibe3D4ZB1N-SqYVt4g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <35073.1480362772.1@critter.freebsd.dk>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Nov 2016 19:52:52 +0000
Message-ID: <35074.1480362772@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@phk.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-6.8
X-W3C-Hub-Spam-Report: AWL=0.013, BAYES_00=-1.9, RP_MATCHES_RCVD=-2.899, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1cBRzJ-0004Lv-Bb e680dcfaf76a9c2dc7dc8e7702e09e9c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Live Byte Ranges
Archived-At: <http://www.w3.org/mid/35074.1480362772@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33025
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

--------
In message <CAOdDvNrrLfh0yV4UdBN_HpHNfD024Kufibe3D4ZB1N-SqYVt4g@mail.gmail.com>
, Patrick McManus writes:

>To summarize briefly - this addresses the problem of addressing byte ranges
>of dynamic (growing) content. A number of solutions have seen false starts
>in this space previously, but this one has a shot at being compatible with
>existing infrastructure.

Varnish will almost certainly implement whatever comes out of this.

Notes from our mumblings in the project:

The "Very Large Value" solution it is brittle in more ways than is
desirable, but try as we may, we don't see any simpler/better ways
of doing it without negotiation/hints.

We suggest to either put a "Quite Large" lower limit on "Very Large
Value", or better yet:  Make it a magic value large enough to not
be a problem relative to actual Range requests.  If we keep with
the 9's motif from the draft, we suggest 999999999999999999 which
doesn't needlessly provoke 64-bit sign issues.

Typo on page 3: "accessable"


-- 
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.