You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see now that we have both enums RTCIceGatheringState and RTCIceGathererState. The former aggregating the latter over possibly many ICE transports in a PeerConnection.
@steveanton Within the RTCIceTransport object, we have RTCIceGathererStategatheringState to express the gathering state of an individual RTCIceTransport, and an ongatheringstatechange EventHandler for when the state changes. Within the RTCPeerConnection we have RTCIceGatheringStateiceGatheringState which represents the aggregate gathering state, and an onicegatheringstatechange EventHandler for when the state changes. While the enum values are the same, the meanings are different. In ORTC's RTCIceGatherer, we have RTCIceGathererStatestate and an onstatechange EventHandler.
The RTCIceTransport has an attribute
gatheringState
of typeRTCIceGathererState
. It also fires an event of typeicegatheringstatechange
.Would it make sense to use the same name for the enum and the attribute/event type?
Proposal:
gatheringState
togathererState
icegatheringstatechange
toicegathererstatechange
(and associated event handler attribute)The text was updated successfully, but these errors were encountered: