W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2011

Re: "onaddstream" and beyond

From: Aleksandr Avseyev <alexn74@gmail.com>
Date: Mon, 28 Nov 2011 10:30:09 -0800
Message-ID: <CALBppDiUbmEUq9ois=_kZewvim48EDaPhxtvAnt_YZ2mbgK+vQ@mail.gmail.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Just a thought. Why we can't stay with #1 option but also add an extra
event OnDataReceived() as well? As some people in the original discussion
thread, I see use cases where it may be useful.

On Fri, Nov 18, 2011 at 1:40 AM, Stefan Håkansson LK <
stefan.lk.hakansson@ericsson.com> wrote:

> Group,
>
> recently there has been some discussion (the starting point was <
> http://lists.w3.org/Archives/**Public/public-webrtc/2011Nov/**0015.html<http://lists.w3.org/Archives/Public/public-webrtc/2011Nov/0015.html>>)
> on when the "addstream" event should fire (and a MediaStream object should
> be handed over to the application):
>
> a) Should it be when the signaling setting up the associated RTP-streams
> over the PeerConnection happens?
>
> or
>
> b) Should it be when there is some data arriving (in at least one track)
> for the MediaStream?
>
> I think we've have concluded that there is a need for the application to
> know when an incoming MediaStream has any activity in it. This is automatic
> in the b) solution as the MediaStream object will not be available before
> there is any content. But with the a) model, there could be an attribute,
> or event fired (possibly on the track level), in the MediaStream object
> that informs the application on when there is any media actually streaming.
>
> So basically there are two options:
>
> 1) Only create MediaStream objects when there is any media streaming
>
> 2) Create MediaStream objects immediately, and have properties of the
> MediaStream tell the application whether or not any media is streaming
>
> Currently in the spec, model 1) is used. This is valid both for
> getUserMedia (which operates asynchronously) and when an incoming stream is
> being set up in the PeerConnection.
>
> The question to this group is: should we stay with this model, or should
> we move to model 2)? I think regardless of model selected, it should be
> applied to both getUserMedia (i.e., if model 2 is selected, a MediaStream
> object is delivered immediately, and the application can detect when there
> is any media streaming in it) and PeerConnection creating MediaStreams.
>
> I think we need to select one model! What are your preferences?
> (Personally my preference would be to stay with 1) as it is to me
> conceptually simpler and that there are fewer things to add/change in the
> spec -  I worry about our schedule :-) ).
>
> Stefan
>
>


-- 

------------------------------
Regards, Aleksandr Avseyev (Futurewei Research Lab)
www.pictures2.com
Received on Monday, 28 November 2011 18:30:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:26 UTC