Release 2.4.0

NEW FEATURES

Backend clients are now compatible with REST API 2.3.0, adding methods:

Session.close(): close a Session from your backend
Session.forceDisconnect(): force some user to leave a Session
Session.forceUnpublish(): force some user to unpublish a Publisher from a Session
Session.fetch(): bring Session information from OpenVidu Server
OpenVidu.fetch(): bring information from every active Session from OpenVidu Server

You can call methods Session.fetch() and OpenVidu.fetch() to bring the current status of sessions from OpenVidu Server. You can consult now directly from OpenVidu Java Client / OpenVidu Node Client all the active sessions with OpenVidu.getActiveSessions() / OpenVidu.activeSessions and the active connections of a session with Session.getActiveConnections() / Session.activeConnections.

Event recordingStopped event now has reason property. Can be:

"recordingStoppedByServer": the recording was stopped by the application (using REST API, OpenVidu Java Client or OpenVidu Node Client)
"lastParticipantLeft": if the Session was configured for automatic recording (RecordingMode.ALWAYS, check OpenVidu Node Client docs for more info), then it stopped because the last participant left the session
"sessionClosedByServer": the recording stopped because the session was forcibly closed by the application (using REST API, OpenVidu Java Client or OpenVidu Node Client)
"openviduServerStopped": the recording stopped because OpenVidu Server process unexpectedly stopped (cannot be guaranteed)

Added a generic fullscreen button which will set as fullscreen element the entire component
Local video toolbar shown on fullscreen
User's nickname update process is now less intrusive (pop-up removed, simple text input instead)
Updated every dialog: now they appear inside of the component (center position), instead of appended to DOM body
The chat component is integrated in the layout for a better experience
New close chat button (top right corner)
New send button (bottom right corner)
New avatar user in each message. A new snapshot image will be displayed with each new message

OpenVidu Server dashboard test could sometimes fail because of a misuse of TURN server
OpenVidu Java Client: pending requests bug fixed
Remote Stream status properties are now properly updated when calling Session.publish, Session.unpublish and Session.publish for the same Publisher object (having unpublished audio or video in between the calls)