- From: Peter Thatcher <pthatcher@google.com>
- Date: Tue, 20 May 2014 12:03:22 -0700
- To: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Cc: "public-ortc@w3.org" <public-ortc@w3.org>
Received on Tuesday, 20 May 2014 19:04:30 UTC
I agree. Even if we have a setTransport, the attribute should be readonly. And for the time being, I thought we agreed to leave out setTransport. On Tue, May 20, 2014 at 12:01 PM, Bernard Aboba <Bernard.Aboba@microsoft.com > wrote: > In the Editor's draft, we have: > > partial interface RTCDtlsTransport { > attribute RTCIceTransport transport; > }; > > partial interface RTCRtpSender { > attribute RTCDTlsTransport transport; > }; > > partial interface RTCRtpReceiver { > attribute RTCDTlsTransport transport; > }; > > Should these attributes be readonly? That is what was proposed today in > W3C WEBRTC. > > If the desire is to change the transports, shouldn't we have a setter to > accomplish this? > > >
Received on Tuesday, 20 May 2014 19:04:30 UTC