Re: [apps-discuss] tail -f over HTTP -- what am I missing?

Larry Masinter <masinter@adobe.com> Wed, 30 April 2014 14:55 UTC

Return-Path: <masinter@adobe.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7002B1A6F03 for <apps-discuss@ietfa.amsl.com>; Wed, 30 Apr 2014 07:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 ZGSgN2lj04Vp for <apps-discuss@ietfa.amsl.com>; Wed, 30 Apr 2014 07:55:44 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id BFC1A1A08F1 for <apps-discuss@ietf.org>; Wed, 30 Apr 2014 07:55:44 -0700 (PDT)
Received: from BL2PR02MB307.namprd02.prod.outlook.com (10.141.91.21) by BL2PR02MB305.namprd02.prod.outlook.com (10.141.91.17) with Microsoft SMTP Server (TLS) id 15.0.929.12; Wed, 30 Apr 2014 14:55:36 +0000
Received: from BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) by BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) with mapi id 15.00.0921.000; Wed, 30 Apr 2014 14:55:36 +0000
From: Larry Masinter <masinter@adobe.com>
To: Mark Nottingham <mnot@mnot.net>, Nico Williams <nico@cryptonector.com>
Thread-Topic: [apps-discuss] tail -f over HTTP -- what am I missing?
Thread-Index: AQHPX+cCYXBMJYdJbU2xdvTXNTreYpsmbxiAgAJQ5oCAAObcAIAAAc0g
Date: Wed, 30 Apr 2014 14:55:36 +0000
Message-ID: <69092435372146fe921ac8fbc9ba78f6@BL2PR02MB307.namprd02.prod.outlook.com>
References: <CAK3OfOikH1ttqZ2TQPSK32FPoR=ReYEMUYQ88=X9LUD2N-ySzg@mail.gmail.com> <712251FA-8918-43DD-B987-72010D603A06@mnot.net> <CAK3OfOh+wi_11P_8V8NaZ7yobkxR0Zm--cUFFyw936mVaCBgQQ@mail.gmail.com> <D82CE0E7-7830-40F6-B4D3-95DE5B264C5C@mnot.net>
In-Reply-To: <D82CE0E7-7830-40F6-B4D3-95DE5B264C5C@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.184.24.49]
x-forefront-prvs: 0197AFBD92
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(199002)(189002)(46102001)(87936001)(2656002)(15202345003)(76482001)(77982001)(76576001)(99396002)(99286001)(86362001)(31966008)(74502001)(74662001)(81342001)(81542001)(33646001)(83322001)(80976001)(19580395003)(4396001)(101416001)(92566001)(85852003)(83072002)(15975445006)(74316001)(77096999)(54356999)(20776003)(79102001)(80022001)(66066001)(76176999)(50986999)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR02MB305; H:BL2PR02MB307.namprd02.prod.outlook.com; FPR:BD8AF6B8.143E2CDA.61D35F00.9FAA923D.20159; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (: adobe.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/LhIk1Sria7V507xRmy017QnNCBg
Cc: Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] tail -f over HTTP -- what am I missing?
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 14:55:46 -0000

>> What were Range requests built for?
> Mostly, interacting with PDFs, AIUI.

http://tools.ietf.org/html/draft-ietf-http-range-retrieval-00
notes that restarting partial downloads was also an original motivation. 

For some reason,  I had expected the web to migrate to using
compound documents
http://en.wikipedia.org/wiki/Compound_document

but to avoid having to download the entire package before you 
could start  rendering.  

I think MPEG-Dash designers considered using range retrieval
but decided it was too unreliably available (many proxies
not doing range retrieval right).

Larry