Re: [rtcweb] a couple of comments on the latest API draft
Stefan Håkansson <stefan.lk.hakansson@ericsson.com> Sat, 22 October 2011 06:52 UTC
Return-Path: <stefan.lk.hakansson@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B16E621F86FF for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 23:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.224
X-Spam-Level:
X-Spam-Status: No, score=-6.224 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5MeNxwjib-4N for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 23:52:18 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 8C30521F86A5 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 23:52:18 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-e4-4ea26820181a
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id C2.9F.20773.02862AE4; Sat, 22 Oct 2011 08:52:16 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Sat, 22 Oct 2011 08:52:15 +0200
Message-ID: <4EA2681F.2090808@ericsson.com>
Date: Sat, 22 Oct 2011 08:52:15 +0200
From: Stefan Håkansson <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15
MIME-Version: 1.0
To: "robert@ocallahan.org" <robert@ocallahan.org>
References: <CAOp6jLZSYBK8ssESoAFtW_5dZkFYVi5NbraB-GF0mYnjs8_QNw@mail.gmail.com>
In-Reply-To: <CAOp6jLZSYBK8ssESoAFtW_5dZkFYVi5NbraB-GF0mYnjs8_QNw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] a couple of comments on the latest API draft
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Oct 2011 06:52:19 -0000
Rob, thanks for providing this input. However, the right place to discuss this kind of things is the public-webrtc@w3.org list (cc'd), not the IETF rtcweb list. Thanks, Stefan (one of the webrtc chairs) On 10/21/2011 10:53 PM, Robert O'Callahan wrote: > http://dev.w3.org/2011/webrtc/editor/webrtc-20111017.html > > I'm not sure that "blackness" is the appropriate output for a finished > MediaStream. HTML media elements that aren't playing anything are > transparent. For consistency, it's probably better for MediaStreams that > aren't playing anything to also be transparent. > > When a |MediaStream > <http://dev.w3.org/2011/webrtc/editor/webrtc-20111017.html#mediastream>| > object ends for any reason (e.g. because the user rescinds the > permission for the page to use the local camera, or because the data > comes from a finite file and the file's end has been reached and the > user has not requested that it be looped, or because the stream > comes from a remote peer and the remote peer has permanently stopped > sending data, it is said to be finished . > > > What if the user reinstates permission for the page to use a camera, or > the author modifies the source to add looping or otherwise replenish the > data (e.g. by restarting the source via some API)? In general, > especially as we add more sources, it's going to be hard to ensure that > the ended/finished state (I think probably you should remove all > mentions of "finished" in favour of "ended") is truly permanent. > Certainly if we allow arbitrary media elements to be used as sources (as > I think we will want to), the author can cause the media element to play > again after it's finished. > > I'm not sure what to do about this, but if we could allow MediaStreams > to exit the "ended" state, that would be good. > > Rob > -- > "If we claim to be without sin, we deceive ourselves and the truth is > not in us. If we confess our sins, he is faithful and just and will > forgive us our sins and purify us from all unrighteousness. If we claim > we have not sinned, we make him out to be a liar and his word is not in > us." [1 John 1:8-10]
- [rtcweb] a couple of comments on the latest API d… Robert O'Callahan
- Re: [rtcweb] a couple of comments on the latest A… Stefan Håkansson
- Re: [rtcweb] a couple of comments on the latest A… Harald Alvestrand
- Re: [rtcweb] a couple of comments on the latest A… Robert O'Callahan
- Re: [rtcweb] a couple of comments on the latest A… Robert O'Callahan