Skip to content

Releases: rtc-io/rtc-switchboard

2.2.0

15 Jan 08:06
Compare
Choose a tag to compare

The switchboard now emits a peer:connect event when a new client connects to the switchboard and a peer:disconnect when the connection is closed.

2.1.0

28 Oct 06:58
Compare
Choose a tag to compare

Disable automatic primus timeout disconnection. This provides compatibility with [email protected] (and above) as it no longer attempts to send primus::ping:: messages.

2.0.0

22 Oct 05:25
Compare
Choose a tag to compare

In line with a move towards a world without peer:leave messages (see rtc-io/rtc-signaller#26) the switchboard no longer distributes /leave messages when a signaller disconnects from the server. This is a much better situation as relying on peer:leave messages or other "I'm always connected" mechanisms provides a false sense of security.

1.2.0

08 Oct 02:21
Compare
Choose a tag to compare

Send 404 responses for any websocket endpoints that are not actively listening for websocket connections.

1.1.0

01 Oct 09:48
Compare
Choose a tag to compare

This release fixes a few things that had been left out of the 1.0.0 release that were previously present in the 0.x releases:

  • switchboard.library() provides a function(req, res) handler for use in http servers.
  • The switchboard instance once again generates data events that can be used to track switchboard behaviour.

1.0.0

01 Oct 09:44
Compare
Choose a tag to compare

This is a fairly major overhaul of the internals of the switchboard while maintaining compatibility with the behaviour of the switchboard as it was in the 0.x releases.

There are a few things to be aware of with this release:

  • switchboard.sparks is now switchboard.peers but still remains as a collections/fast-map

  • The function signature for handlers has changed to match the following:

    function(mgr, spark, parts, primus, opts) {
    }
  • The switchboard is now an instance of mbus rather than an EventEmitter.