RE: Issue 141: Mandatory "kind" in RTCRtpReceiver constructor from Bernard Aboba on 2014-08-05 (public-ortc@w3.org from August 2014)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Tue, 5 Aug 2014 18:30:48 +0000
To: Peter Thatcher <pthatcher@google.com>
CC: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <c11545b2507b4f328187bfeb39ca0c93@SN2PR03MB031.namprd03.prod.outlook.com>

Peter Thatcher said: 

"Right, and I think this is easy to do in the implementation.  In fact,
if we had the JS pass down  the kind explicitly, it would still need
to do so anyway, because if the JS passes down kind=audio, and then
passes down video codecs, the implementation should complain.   So, it
needs to check either way, and I'd prefer not having duplicate,
possibly contradictory parameters."

[BA] Question:  would it make sense to include "kind" in RTCRtpCodecParameters?  It is already in RTCRtpCodecCapability.

Received on Tuesday, 5 August 2014 18:31:19 UTC