On 10/04/2012 11:04 PM, Anant Narayanan wrote: > On 10/04/2012 04:29 AM, Harald Alvestrand wrote: >> I think we decided some time ago that in order to limit our impact on >> the namespace, we'd prefix our interfaces and data types with "RTC". >> >> It seems that we've mostly done this, but not fully; the following >> interfaces are not prefixed: >> >> - DataChannel interface >> - MediaStreamEvent >> - DataChannelEvent >> - DataChannelState enum >> - DataChannelInit dictionary >> - DataChannelEventInit dictionary >> - MediaStreamEventInit dictionary > > Only interfaces that have a global constructor need to be prefixed. > Currently, that means DataChannelEvent and MediaStreamEvent. But is there an argument for not using the prefix? In particular DataChannel - this seems like an RTC-only construct. > > The other constructors defined by the spec are: RTCSessionDescription, > RTCIceCandidate, RTCPeerConnection, and RTCPeerConnectionIceEvent, > which are already prefixed. > > If there are no objections, I will change the names for > DataChannelEvent and MediaStreamEvent! No objection from me here! > > -AnantReceived on Friday, 5 October 2012 09:06:25 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:34 UTC