Releases: rtc-io/rtc
Updated dependencies
Rebuilt with latest rtc-quickconnect@^4
dependencies.
3.3.0
Rebuild with updated rtc-quickconnect
version, which in turn uses updated (more robust) signalling.
3.1.2
3.0.0
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 byRTC
after creation, rather a validrtc-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 thelocalContainer
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.