Release v2.3.0

New archiving features:

• Automatically archived sessions -- See the "archiveMode" option of the opentok.createSession() method.
• Individual archiving -- See the "outputMode" option of the opentok.startArchive() method.
• Video or Audio only archives -- See the "hasAudio" and "hasVideo" options of the opentok.startArchive() method.
• Paused archives -- When no clients are publishing to a session being archived, its status changes to "paused". See archive.status.

Other improvements:

• Adds support for node 0.12.x and io.js (#89, #94)
• Uses npm package "opentok-token" as the token encoder (#92)
• Documentation improvements

Release v2.2.5

• generateToken() now throws when invalid options are passed instead of returning false #62
• Fixes broken session.generateToken() issue due to bad capturing of this #58
• generateToken() now rounds the expireTime option down to a whole number #76
• No longer mutates the options passed into createSession() (#77) or generateToken() (#90).
• Handles 503 server errors #80 (thanks @ametaireau)
• Fixed typo in an error message #81 (thanks @radekk)

Release v2.2.4

This update adds the following changes:

• Augmented test suite to include conditions where archive JSON contains new status 'expired' or unexpected properties.
• Added support for HTTP/HTTPS proxies by adding a proxy key to the optional config parameter in the OpenTok constructor. This is useful inside tightly controlled (corporate) infrastructure where all HTTP traffic must be proxied. See: #41.
• Added a default timeout of 20 seconds for HTTP requests. See: #51.
• OpenTok instances now expose their API URL via the apiUrl property. This is useful when the API URL may have been set and/or the consumer would like to query the current value. See: #39.
• The OpenTok constructor now throws errors when an invalid required property is provided (rather than returning an Error object). See: #38.
• The opentok.createSession() method now throws errors when no callback is provided (rather than returning an Error object). See: #42.

Release v2.2.3

The default setting for the createSession() method is to create a session with the media mode set
to relayed. In previous versions of the SDK, the default setting was to use the OpenTok Media Router
(media mode set to routed). In a relayed session, clients will attempt to send streams directly
between each other (peer-to-peer); if clients cannot connect due to firewall restrictions, the
session uses the OpenTok TURN server to relay audio-video streams.

Release v2.2.0

This version of the SDK includes support for working with OpenTok 2.0 archives. (This API does not
work with OpenTok 1.0 archives.)

The createSession() method has changed to take one parameter: an options object that has location
and mediaMode properties. The mediaMode property replaces the properties.p2p.preference
parameter in the previous version of the SDK.

The generateToken() has changed to take two parameters: the session ID and an options object that has role, expireTime and data properties.