6.2.1

Only "re-announce" on reconnection if this is not the initial connection attempt.

6.2.0

This release fixes bugs with the outbound message queue not being reset when a websocket (or other transport sink) has been closed. Fixing this allows the signaller to properly reconnect whereas before it was failing in it's reconnection.

6.0.0

• Removed the ability to set metadata, by removing the metadata function (which was deprecated in the final version of 5.x)
• Changed signalling metadata to only include the sender id as opposed to a JSON payload of metadata.

5.1.0

• When a signaller is asked to send a message (including announce notifications) it will automatically reconnect if disconnected.
• Exposed the signaller.connect() function in instances where a connection should be manually initiated.
• Added the autoconnect initialization option (default: true) which controls both initial signaller connection and the automatic connection when sending behaviour.

5.0.0

This is a significant rewrite of the how the underlying communication is implemented within the signaller. Notably:

• All communication is now done via a pull-stream interface, which significantly simplifies connectivity.
• There is no concept of WebSocket connectivity with a signaller now at all, but simply combine this with either rtc-switchboard-messenger or just messenger-ws to get this connectivity. This is what rtc-quickconnect will do when it is upgraded to use this version of the signaller.
• Update peer:filter event arguments to match other peer:* events (#19)
• Combined with some changes in [email protected] a signaller will no longer emit peer:leave messages when another peer connected to the signalling server leaves the room. This has been done to prevent reliance on what should be considered a temporary connection state.

4.0.0

With this release of rtc-signaller we move to using a pure WebSocket client where possible for connecting with our server side signalling layer (either rtc-switchboard or another compliant implementation). See #24 for a broader discussion on this topic.

This release will be compatible with previous versions of the switchboard, however, it is best if it is communicating with a switchboard instance 1.2.0 or above.

Upgrading to version 4.0.0 of the signaller should be a trivial operation, but should be analysed given the changes to how websocket connections are established. As a result, rtc-quickconnect will continue to use the 3.x release of the signaller until all known alternative switchboard implementations have been properly tested. To aid this, the rtc-signallercheck tool will be upgraded to use version 4.0.0 soon to aid this effort.

In addition to the above, the following are a few noteworthy changes that have occurred in this release:

• Attempt to connect to the / endpoint rather than /primus endpoint, but support connecting to the /primus endpoint after a short timeout period. This is a soft implementation of (1).
• Implement ping (2).
• Continue to send primus::ping:: messages in addition to /ping messages to ensure that primus is kept alive as well as the internal switchboard logic (which is currently nothing).

3.0.0

While the external interface of the signaller remains the same through this major version change (and all tests pass without modification), the change across to using mbus rather than event emitter warrants the change.

• Use cuid package for unique id generation
• Use mbus package for event distribution

2.5.0

Added the ability to customise the path from which primus.js is loaded from the signalling host. By default this is loaded from the /rtc.io/primus.js path but this can now be customised by providing a primusPath option when creating the signaller (or when creating quickconnect) to request the signaller load primus from an alternative path.