RE: Issue 143: SSRC Conflict

How about the following?

partial interface RTCRtpSender : RTCStatsProvider {
                attribute EventHandler?    onssrcconflict;
};

onssrcconflict of type EventHandler, , nullable
This event handler, of event handler type RTCSsrcConflictEvent, must be supported by
all objects implementing the RTCRtpSender interface. This event MUST be fired if an
SSRC conflict is detected.

6.4 RTCSsrcConflictEvent

The onssrcconflict event of the RTCRtpSender object uses the RTCSsrcConflictEvent interface.

Firing an RTCSsrcConflictEvent event named e with an ssrc means that an event with the name e,
which does not bubble (except where otherwise stated) and is not cancelable
(except where otherwise stated), and which uses the RTCSsrcConflictEvent interface
with the ssrc attribute set to the conflicting SSRC must be created and dispatched
at the given target.

dictionary RTCSsrcConflictEventInit : EventInit {
    unsigned long? ssrc;
};

[Constructor(DOMString type, RTCSsrcConflictEventInit eventInitDict)]
interface RTCSsrcConflictEvent : Event {
    readonly    attribute unsigned long ssrc;
};

6.4.1 Attributes

ssrc of type unsigned long, readonly
The ssrc attribute represents the conflicting SSRC that caused the event.

6.4.2 Dictionary RTCSsrcConflictEventInit Members

ssrc of type unsigned long, nullable
The ssrc attribute represents the conflicting SSRC that caused the event.

Received on Wednesday, 6 August 2014 19:44:04 UTC