Skip to content

Releases: rtc-io/rtc-quickconnect

2.4.0

17 Jul 04:25
Compare
Choose a tag to compare
  • Added the endCalls function which can be used to terminate any active connections to peers without leaving the signalling server.

2.0.0

04 Aug 04:55
Compare
Choose a tag to compare

The 2.0 release of quickconnect includes a major upgrade to rtc-signaller and improved compatibility with WebRTC integration with existing node modules (e.g. node-webrtc). A summary of all the changes since 1.0.5 to 2.0.0 are outlined below:

  • Upgraded to use [email protected]
  • Improved compatibility with pure websocket signalling (not requiring primus) thanks to the rtc-signaller upgrade.
  • Introduction of a connection:created event to allow early attachment to a RTCPeerConnection object prior to attempting to "finalize a call".
  • Replaced the collections/fast-map with a simple map implementation to reduce the overall distribution size of quickconnect in the browser.

1.0.0

05 May 00:25
Compare
Choose a tag to compare

There have been some reasonably significant changes in the upgrade to [email protected]. Primarily this has been around the different events that are emitted by quickconnect, and also the arguments that are passed to events.

With regards to the arguments passed to events, we have looked to standardize with all events including the id of the relevant peer being the first argument in all cases. Where there were old events with a different format those have been removed and replaced with new events.

The following table lists a mapping for old to new events:

Old Event New Event
peer:connect call:started
peer:leave call:ended NOTE: peer:leave still fires, but call:ended is a better choice in most cases
%label%:open channel:opened:%label%
%label%:close channel:closed:%label%

In addition to these changes, there are a number of new events that are also documented in the README:

General data channel events:

  • channel:opened
  • channel:closed

Media Stream Events

  • stream:added
  • stream:removed

That's pretty much it, you just need to ensure that your event handlers match the new format (again, see the events documentation in the README) and everything should work just fine.