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).