Yeah, I would love to transition all this stuff to the Streams API, but I don't want to block fixing this on a huge project like that. On Mon, May 18, 2015 at 4:19 PM, Göran Eriksson AP < goran.ap.eriksson@ericsson.com> wrote: > > Resent-Date: Monday 18 May 2015 21:58 > > >On 18 May 2015 at 12:56, Martin Thomson <martin.thomson@gmail.com> wrote: > >> On 18 May 2015 at 12:53, Iñaki Baz Castillo <ibc@aliax.net> wrote: > >>> Which is the "streams API" in the JS land? > >> > >> I think that this is the latest, but these things move around a bit: > >> https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm > > > > > >And it did (or I was wrong): https://streams.spec.whatwg.org/ > > RightŠ > > Now it is getting interesting: we have WebRTC stats API, Streams API and > perhaps also feedback methods (events) on the > RTCDataChannel API as proposed by Benjamin. > > I think Benjamin brought up a valid use case and a pretty well-defined one > at that that should be addressed here and now. > > There there may be that there is another issue here, namely a review of > the stats and feedback situation of WebRTC API¹s > but that should be addressed separately from the question of feedback > event on the RTCDataChannel I think. > > If possible at least... > > > > >
Received on Monday, 18 May 2015 20:29:53 UTC