Re: Issue with "bytes" Range Unit and live streaming

Amos Jeffries <squid3@treenet.co.nz> Fri, 15 April 2016 12:41 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 53BDB12E300 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 05:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.917
X-Spam-Level:
X-Spam-Status: No, score=-7.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, 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 5jQpjnrzTGOP for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 05:41:33 -0700 (PDT)
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 E841312E2FA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 15 Apr 2016 05:41:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ar2zf-0000EY-J5 for ietf-http-wg-dist@listhub.w3.org; Fri, 15 Apr 2016 12:37:03 +0000
Resent-Date: Fri, 15 Apr 2016 12:37:03 +0000
Resent-Message-Id: <E1ar2zf-0000EY-J5@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <squid3@treenet.co.nz>) id 1ar2zb-0008I2-EU for ietf-http-wg@listhub.w3.org; Fri, 15 Apr 2016 12:36:59 +0000
Received: from [121.99.228.82] (helo=treenet.co.nz) by maggie.w3.org with esmtp (Exim 4.80) (envelope-from <squid3@treenet.co.nz>) id 1ar2za-0007Yl-4g for ietf-http-wg@w3.org; Fri, 15 Apr 2016 12:36:59 +0000
Received: from [192.168.20.251] (unknown [121.98.40.13]) by treenet.co.nz (Postfix) with ESMTP id 5BB6FE6F6C for <ietf-http-wg@w3.org>; Sat, 16 Apr 2016 00:36:27 +1200 (NZST)
To: ietf-http-wg@w3.org
References: <57102718.7010900@ecaspia.com>
From: Amos Jeffries <squid3@treenet.co.nz>
Message-ID: <5710E043.9020505@treenet.co.nz>
Date: Sat, 16 Apr 2016 00:36:19 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <57102718.7010900@ecaspia.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=121.99.228.82; envelope-from=squid3@treenet.co.nz; helo=treenet.co.nz
X-W3C-Hub-Spam-Status: No, score=-4.3
X-W3C-Hub-Spam-Report: AWL=-1.153, BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1ar2za-0007Yl-4g 78cd4b6a83e167f7d9a80838761edcb9
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Issue with "bytes" Range Unit and live streaming
Archived-At: <http://www.w3.org/mid/5710E043.9020505@treenet.co.nz>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31473
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>

On 15/04/2016 11:26 a.m., Craig Pratt wrote:
> Hello all,
> 
> We have a use case where we are "live streaming" media over HTTP. As with other 
> (non-segmented) HTTP streaming applications, our live streaming solution has the 
> HTTP client perform a GET on a URI representing the live audio or video content 
> stream and with the server progressively returning data using chunked transfer 
> coding. The data returned to the server is "live" so long as the client reads 
> data as quickly as it's generated - with TCP flow control allowing the client's 
> reading of the response data to be paced to the live chunk generation of the 
> HTTP server.

Please be careful not to rely on the chunks arriving at the client in
the same sizes as were sent.

The chunked encoding is a hop-by-hop feature so any HTTP intermediary
which they travel through may re-code the chunk sizes according to its
own output needs.

Cheers
Amos