Re: [hybi] Framing take IV

Ian Hickson <ian@hixie.ch> Wed, 04 August 2010 04:26 UTC

Return-Path: <ian@hixie.ch>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13D703A6BB3 for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 21:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.357
X-Spam-Level:
X-Spam-Status: No, score=-2.357 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZBt1gk0m1KB for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 21:26:47 -0700 (PDT)
Received: from homiemail-a43.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 167BB3A6BAE for <hybi@ietf.org>; Tue, 3 Aug 2010 21:26:47 -0700 (PDT)
Received: from homiemail-a43.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a43.g.dreamhost.com (Postfix) with ESMTP id 2FA658C065; Tue, 3 Aug 2010 21:27:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=hixie.ch; h=date:from:to:cc :subject:in-reply-to:message-id:references:mime-version: content-type; q=dns; s=hixie.ch; b=W/ANw8ZvEmAVtR7bPl0XID//RETzP liB+3flmaH9lVoSo4TkoR7g5NUBGz37as/OP05HfV7al1QvAmeCxa/KHAbOo1voF Uqk+L+fE0L375qQWzsNoBv5tHDlwiqq9nLiM82y9qeuf0y95W0UM2ba0FJ6+wNBN keE3uETgkAhxwM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=DnkyeKxYhP7YmfeL75ZYc3Yqt9A=; b=OSj p2sCvT5dsB1oUVsOVhLgfXD0g2+gUKzYd/D5NHnP4cMZQ5N7kD2Sq7/+AZt744Zj 25FojVqr/Z6sniFz4vPeYL1tn9SuG5yzVHECKr9XBcCSGroSNp8GYCs80jZ3a4hf tHdZ7qIdaWyhGP4eoUSIOXeNRg/C60CGloq2rbTk=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a43.g.dreamhost.com (Postfix) with ESMTPSA id 207158C05F; Tue, 3 Aug 2010 21:27:16 -0700 (PDT)
Date: Wed, 04 Aug 2010 04:27:15 +0000
From: Ian Hickson <ian@hixie.ch>
To: "Ian Fette (イアンフェッティ)" <ifette@google.com>
In-Reply-To: <AANLkTinp7UmROSCRSvuj_AKcMT4OnhWebPCD-z_60LZZ@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1008040424580.5947@ps20323.dreamhostps.com>
References: <AANLkTinyrDoG5d_Ur6HVRy=SgMPjLzJtpJ++Ye=1DQdj@mail.gmail.com> <Pine.LNX.4.64.1008040050040.5947@ps20323.dreamhostps.com> <28A6543A-5CA6-42B7-8D2E-F5511EE20008@apple.com> <4C58C2F6.8050608@caucho.com> <Pine.LNX.4.64.1008040132190.5947@ps20323.dreamhostps.com> <4C58C4C8.5020900@caucho.com> <Pine.LNX.4.64.1008040139520.5947@ps20323.dreamhostps.com> <AANLkTinp7UmROSCRSvuj_AKcMT4OnhWebPCD-z_60LZZ@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-1555694626-1169139505-1280896035=:5947"
Cc: hybi@ietf.org
Subject: Re: [hybi] Framing take IV
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2010 04:26:53 -0000

On Tue, 3 Aug 2010, Ian Fette (ã~B¤ã~B¢ã~C³ã~C~Uã~B§ã~C~Cã~C~Fã~B£) wrote:
>
> We're adding a voice input capability, and we want to start sending the 
> user's voice up as soon as they start speaking, without waiting for the 
> recording to be finished so that we can start backend processing. Yes, 
> we could probably break it into multiple messages, but given that 
> semantically it's a single message, this is a case where we would want 
> to start sending data before knowing its length. Ditto for hooking up a 
> video camera and sending that data to some sort of web service.

I would hope that audio and video data would get sent using the 
ConnectionPeer mechanism, ideally UDP-based (though that protocol hasn't 
even been sketched out yet), not over TCP-based WebSockets.

But if we do want to send live audio data over WebSockets, then we're 
going to do a bunch of work, like adding microphone support to the Web 
platform. When we do that, we can easily add a live-stream-specific frame 
code that sends fixed size blobs of audio and/or video streams. The 
protocol supports that as an extension fine, without needing to define how 
fragmentation works today.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'