The **rtc‑signaller** library is a transport‑agnostic signalling layer for WebRTC that works with any messenger (e.g., WebSocket, memory, or custom pub/sub) to enable peers to discover each other, exchange connection state, and coordinate RTCPeerConnection setup. It’s aimed at developers building WebRTC‑enabled applications who need a flexible, message‑stream‑based signalling engine that can operate over any transport or signalling server without being tied to a specific backend.
Total donated
Undistributed
Share with your subscribers:
Recipients
How the donated funds are distributed
Support the dependencies of rtc-io/rtc-signaller
Cherry pickable JS functions
Collision-resistant ids optimized for horizontal scaling and performance. For node and browsers.
Simple String Variable Replacement Formatter
If Node's EventEmitter and Eve were to have a child, it might look something like this
pull-stream with a push interface
minimal pull stream
Core definitions and functions for the rtc.io suite
The core processing logic for the client component of rtc.io signalling
Higher-order functions and common patterns for asynchronous code
Super simple browser testing influenced by testling and smokestack
browser-side require() the node way
Functional thinking inspired DOM helpers (browserify and selective require friendly)
Simple in-memory messaging following the messenger-archetype
A suite of tests that will test how well a custom signaller supports the requirements of rtc-quickconnect and rtc-tools
Signalling for rtc-io components using primus
A specialised messenger-ws implementation that knows how to connect to a rtc-switchboard instance
Formatted TAP output like Mocha's spec reporter
tap-producing test harness for node and browsers
Functional operation helpers (underscore-like) for working with map, filter, reduce, etc
Support the repos that depend on this repository
Top contributors
Recent events
Kivach works on the Obyte network, and therefore you can track all donations.
No events yet