4.2.0

• Added compatibility for [email protected] which now emits "raw message events" with a message: prefix
• No longer are peer:leave messages monitored for P2P connection termination - this will mean that this firefox issue will mean that firefox clients will not correctly get call:ended or similar events for versions of rtc-quickconnect that use rtc-tools >= 4.2.0

4.1.0

• Rename the generic change event on monitor to statechange which more accurately reflects the fact that the iceConnectionState of a peer connection has changed.

4.0.0

Major changes to the underlying mechanism for coupling one connection to another without breaking the API. So while this is not technically a breaking change, it should be something that people opt into rather than get automagically upgraded to.

Primarily the logic rework has been done but breaking a large part of the coupling logic into a new package called rtc-taskqueue which uses a priority queue, readiness measures and incorporates validation logic (thanks to rtc-validator) to do everything we can to ensure that calls to the underlying RTCPeerConnection and associated types are applied in the right order.

In addition to the coupling logic changes, the generic monitor eventemitter has been replaced with a package called mbus that allows events to be communicated through a parent hierarchy giving us the ability to communicate efficiently from the internals of coupling logic to top level events as this functionality is integrated into other rtc.io packages.

3.2.0

Add the ability to provide an iceServerGenerator function when creating a connection using the createConnection function provided by rtc-tools.

Additionally, as this function is called by rtc-quickconnect providing an iceServerGenerator function to quickconnect initialization opts will allow you to specify this function there and have it applied when new connections are created as peers are discovered.

Thanks to @dugancathal for implementing this feature!

3.1.0

Additional events are triggered through the "monitor" event emitter that can be used to track the status of a peer connection during connection negotiation. More details are available on the events at the following url:

https://github.com/rtc-io/rtc-tools/blob/master/docs/coupling-events.md

3.0.0

Removed normalisation of iceServers supplied when creating a new connection. This has been causing unintended side effects when working with Chrome 36, and causes confusion when working with rtc.io modules.