Skip to content

Releases: rtc-io/rtc

Updated dependencies

01 Feb 07:54
Compare
Choose a tag to compare

Rebuilt with latest rtc-quickconnect@^4 dependencies.

3.3.0

30 Apr 01:42
Compare
Choose a tag to compare

Rebuild with updated rtc-quickconnect version, which in turn uses updated (more robust) signalling.

3.1.2

22 Oct 01:08
Compare
Choose a tag to compare

Fixed global leaks (#11) by rebuilding against updated versions of rtc.io packages.

3.0.0

14 Oct 00:20
Compare
Choose a tag to compare

With the 3.0.0 release, the RTC package is firmly focused on delivering you the ability to create media-centric (i.e. video conferencing) WebRTC applications in the easiest way possible. This has involved a significant API overhaul with the following notable changes:

  • The ready event is no longer fired by RTC after creation, rather a valid rtc-quickconnect instance is returned from calling the function. This in turn encourages diving down to the lower layers of rtc.io to build those "slightly different" applications.

  • When the RTC() function is called, some automatic initialization occurs using the default configuration options. With the provided options, local media will be captured using the simple { video: true, audio: true } constraints and the resulting stream injected into the localContainer specified.

    Once media has been successfully captured, we announce ourselves to the signalling server and attempt to connect with any other participants in the room we have announced in. If other participants are present, then their video stream will be added to the remoteContainer as specified in the options.