Wasting no time, the tortoise caught up with Achilles! https://medium.com/@openvidu/openvidu-2-11-0-webhook-service-and-first-version-of-scalability-87a476039cad

Необходимо настроить Travis CI для тестов.

Background

The transition of the RTCPeerConnection to the failed state is a fatal event, but the openvidu-browser does not respond to this.

Problem to solve

Implement RTCPeerConnection: iceconnectionstatechange event
processing and emit openvidu-browser event if it happened.

Possible solutions

Add IRTCPeerConnection: iceconnectionstatechange event
handler to WebRtcPeer and emmit openvidu-browser event from Stream.

Background

At this stage, the method Openvidu.closeWs takes no arguments, but always sets the same parameters code: (4102) and reason: "Connection closed by client". But it would be useful to receive more advanced information, which can explain why the client has closed the connection.

Problem to solve

Enable the library client to set its custom parameters code and reason when calling the method Openvidu.closeWs.

Possible solutions

Add code and reason arguments to the signature of the Openvidu.closeWs Openvidu.closeWs method.

Background

Restore subscription to stream, implemented as follows:

• unsubscribe;
• stream.on (ICEConnectionStateChange);
• When we catch iceconnectionstate = closed we call subscribe.

Everything works well in Chrome and FF, but in Safari after unsubscribe it does not fire iceconnectionstatechange, even though ICEConnection remains in the same state as before unsubscribe, ICEConnectionStateChange does not occur and Pipeline hangs on it. If you pull subscribe right after unsubscribe, Safari (actually any browser) will complain about attempts to add ICE Candidates of a new subscription.

Problem to solve

implement the unsubscribeAsync method as part of the openvidu-browser (similar to subscribeAsync), which will return the resolve only when Stream.disposeWebRtcPeer plays.

Possible solutions

Implement the unsubscribeAsync method of Session.

Part of #8.

Background

There is no readme file in the openvidu-browser project, so there is no information about the project on the project page on npm.

There is no such README.md file in the project of our Spanish colleagues.

Problem to solve

I think that it is worth fixing this annoying mistake.

Possible solutions

Add README.md file to the openvidu-browser project directory.

Revealed from #14

Background

The new QualityValue and FlowQualityChangeEvent has no public access.

Problem to solve

1. In order for the new QualityValue and FlowQualityChangeEvent classes to be publicly available, they must be added to the index.
2. I propose to change the name QualityValue to MediaFlowQualityValue so that it is clear that this is about the quality of the media stream.
3. I propose to add to the MediaFlowQualityValue enumeration the zero position NOT_INITIALIZED

Possible solutions

1. Rename QualityValue to MediaFlowQualityValue.
2. Add NOT_INITIALIZED item into MediaFlowQualityValue.
3. Add MediaFlowQualityValue and FlowQualityChangeEvent into index.

Background

On the server side, an RPC call to the "qualityChanged" method is implemented, which occurs in response to the "MediaFlowInStateChange" events for the publisher and "MediaFlowOutStateChange" for the subscriber.
It is necessary to process a call of this method on the client.

Problem to solve

RPC call handling of the "qualityChanged" method.

Possible solutions

Add Stream.qualityChangedHandler into rpc configuration and emmit event qualityChanged with given quality param.