- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Mon, 24 Aug 2015 20:05:15 +0000
- To: Peter Thatcher <pthatcher@google.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Received on Monday, 24 August 2015 20:05:46 UTC
I agree with your recommendation. On Aug 24, 2015, at 11:57 AM, Peter Thatcher <pthatcher@google.com<mailto:pthatcher@google.com>> wrote: A question came up in the PR for IceTransport.DtlsTransport https://github.com/w3c/webrtc-pc/pull/241<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fw3c%2fwebrtc-pc%2fpull%2f241&data=01%7c01%7cBernard.Aboba%40microsoft.com%7cb2ab43f3b1524af9667608d2acb5da74%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=OLnOR%2bAW9M0j7jopvW4q4KwGpqp5eyJY%2fgaxPe60T%2fo%3d> about the name of the "state" attribute. Which name should we have? Option A (What's in there, simplest name): IceTransport.state IceTransport.onstatechange DtlsTransport.state DtlsTransport.onstatechange Option B (Matches DataChannel, WebSocket, etc): IceTransport.readyState IceTransport.onreadystatechange DtlsTransport.readyState DtlsTransport.onreadystatechange Options C (Matches PeerConnection.iceConnectionState): IceTransport.connectionState IceTransport.onconnectionstatechange DtlsTransport.connectionState DtlsTransport.onconnectionstatechange My vote: state > connectionstate > readystate. What's yours?
Received on Monday, 24 August 2015 20:05:46 UTC