rtc-io/rtc-signaller

Cherry pickable JS functions

Collision-resistant ids optimized for horizontal scaling and performance. For node and browsers.

pull-stream with a push interface

minimal pull stream

Core definitions and functions for the rtc.io suite

Higher-order functions and common patterns for asynchronous code

Super simple browser testing influenced by testling and smokestack

browser-side require() the node way

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

Simple String Variable Replacement Formatter

Functional thinking inspired DOM helpers (browserify and selective require friendly)

If Node's EventEmitter and Eve were to have a child, it might look something like this

The core processing logic for the client component of rtc.io signalling

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