2.5.0
This PR is for the release of 2.5.0 which adds improves on the persistent messages feature.
Dependencies
CDN links (gzipped)
- Skylink library with all dependencies:
-- //cdn.temasys.io/skylink/skylinkjs/2.5.0/skylink.complete.js
-- //cdn.temasys.io/skylink/skylinkjs/2.x/skylink.complete.js
-- //cdn.temasys.io/skylink/skylinkjs/latest/skylink.complete.js
- Skylink library with all dependencies in umd format:
-- //cdn.temasys.io/skylink/skylinkjs/2.5.0/skylink.complete.umd.js
-- //cdn.temasys.io/skylink/skylinkjs/2.x/skylink.complete.umd.js
-- //cdn.temasys.io/skylink/skylinkjs/latest/skylink.complete.umd.js
- Minified with all dependencies:
-- //cdn.temasys.io/skylink/skylinkjs/2.5.0/skylink.complete.min.js
-- //cdn.temasys.io/skylink/skylinkjs/2.x/skylink.complete.min.js
-- //cdn.temasys.io/skylink/skylinkjs/latest/skylink.complete.min.js
API Documentation
https://cdn.temasys.io/skylink/skylinkjs/2.5.0/docs/index.html
IMPROVEMENTS
STORED MESSAGES
- Stored messages can now be retrieved by a room session. The
getStoredMessages
function now takes a second argumentroomSessionId
.roomSessionId
is found in thepeerInfo
object in most event payloads, e.g.PEER_JOINED
. - A room session starts when the first peer joins a room. A room session ends when the last peer leaves the room. Subsequent peers that join the same room, i.e. the same room name, starts a new room session.
PERSISTENT MESSAGE
sendMessage
now takes a fourth argumentpeerSessionId
. IfpeerSessionId
is passed as a parameter, it will replace the peerId as thesenderPeerId
in the retrieved messages.- The
peerSessionId
can be used to attribute the message to a client across sessions.