Release v2.3.0

New archiving features:

• Automatically archived sessions -- See the archiveMode() method of the SessionProperties.Builder class and the ArchiveMode class.
• Audio-only or video-only archives -- See the new ArchiveProperties.Builder class and the hasAudio() and hasVideo() methods.
• Individual archiving -- See the outputMode() method of the new ArchiveProperties.Builder class and the OutputMode class.
• Paused archives -- When no clients are publishing to a session being archived, its status changes to "paused". See Archive.Status.PAUSED.
• OpenTok.listArchives() now returns a new type called ArchiveList. It still implements the List<Archive> interface, so this change is backwards compatible.

Other improvements:

• Support for Oracle JDK 8 (#57)
• Loosens version specifiers to reduce dependency conflicts (#39)
• Updates gradle to version 2.3

Release v2.2.2

This version adds the archive status value of EXPIRED.

Release v2.2.1

This release includes a change to the default media mode for sessions created without the media mode specified. The default media mode is now com.opentok.MediaMode.RELAYED

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

This version of the SDK includes a number of improvements in the API design. These include a number
of API changes. See the OpenTok 2.2 SDK Reference for details on the new API.

The API_Config class has been removed. Store your OpenTok API key and API secret in code outside of the SDK files.

The create_session() method has been renamed createSession(). Also, the method has changed to
take one parameter: a SessionProperties object. You now generate a SessionProperties object using a Builder pattern.

The generate_token() method has been renamed generateToken(). Also, the method has changed to
take two parameters: the session ID and a TokenOptions object.

v2.0.0 - OpenTok on WebRTC compatibility update

In the v2.0.0 release, the createToken method has been updated to be compatible with the OpenTok on WebRTC platform. You are now required to correlate a token with a session ID to be able to successfully create the token. This will make it more difficult for someone to generate their own token, and maliciously enter your session.