-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPARK-532493 webrtc core should expose separate events for ice and connection state #78
SPARK-532493 webrtc core should expose separate events for ice and connection state #78
Conversation
…e connection state
…e connection state
…for-ice-and-connection-state' of https://github.com/webex/webrtc-core into spark-532493-webrtc-core-should-expose-separate-events-for-ice-and-connection-state
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed with @marcin-bazyl's comments. Also left a comment about naming.
eefe004
to
3513785
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, left a minor comment. As I discussed with you offline, since this is technically a breaking change, I would check with the SDK team to make sure they are ok with it, as this might affect some SDK customers. Likely they will need to document this somewhere, so I might wait until you get the ok before merging.
48e0bea
This PR divide evaluating of overall connection state to two separated events.
We have decided that it's useful to have access to both events IceConnectionState and ConnectionState separately.
It's required for JS-SDK to have access directly to the reason of media join failure.