- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Mon, 28 Apr 2014 19:19:25 -0700
- To: Justin Uberti <juberti@google.com>
- Cc: Peter Thatcher <pthatcher@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 28 April 2014 16:51, Justin Uberti <juberti@google.com> wrote: > I thought about it a bit, and I don't really see an issue with making it > arbitrary. This will put the track to be in the specified MS at the other > side, but I don't see a need to force the tracks to be bagged up on the send > side. Why not just put the stream in, not its identifier and avoid the issue? As for the null case, generate a new stream on the remote side for every track that is added that way.
Received on Tuesday, 29 April 2014 02:19:53 UTC