Re: [webrtc-pc] pc.addTrack/removeTrack are confusing and mostly redundant. Mark as legacy?

Maybe we should take a step back in the discussion here.

I hope everyone agrees that we three API iterations in the spec right now. Is the intention to keep all three of them?

It sound to me like keeping multiple version of the APIs make things:

1. very complicated for browser to implement, as multiple APIs will result in unpredictable behavior, especially if developers start mixing the different APIs (which they will do if they all co-exist).
2. confusing to users of the API as they surely assume they can use all of them

So I always expected that at some point in the future we can turn stream and track based APIs off to avoid confusion and delete code which causes confusion.

That's why I'm in favor of marking stream and track based APIs as legacy to indicate to developers that they should not use them going forward.

If the intention here is to keep stream and track based APIs around, then I fear this working group still has a lot of work ahead of it defining all the edge case between the different API versions, because these are clearly underspecified right now.

GitHub Notification of comment by nils-ohlmeier
Please view or discuss this issue at using your GitHub account

Received on Thursday, 1 February 2018 23:56:28 UTC