Re: Naming question to resolve: state vs. readystate vs connectionstate from Iñaki Baz Castillo on 2015-08-24 (public-webrtc@w3.org from August 2015)

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 24 Aug 2015 22:09:27 +0200
To: Peter Thatcher <pthatcher@google.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <CALiegfkVqVAanTVdgU2=X82nEef9gjCs_HtSH8V7-ggKa3Vt4w@mail.gmail.com>

2015-08-24 20:54 GMT+02:00 Peter Thatcher <pthatcher@google.com>:
> My vote: state > connectionstate > readystate.
>
> What's yours?

If just a state is handled by the entity, then "state" sounds good (I
don't like the extra "readyState" of WebSocket, etc, and the
RTCPeerConnection has so many "xxxxxState" properties because it
handles everything all together).


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

Received on Monday, 24 August 2015 20:10:15 UTC