Skip to content
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

Use RxJSPeer for the peer connection pushing/pulling #66

Merged
merged 5 commits into from
Jul 24, 2024

Conversation

third774
Copy link
Collaborator

Sorry for the giant PR, but this was a LOT to refactor 😅

This completely replaces the previous Peer class which was promise based with a Peer class based on RxJS. This approach buys us a lot of reliability inside the non-React boundaries of our logic.

Track acquisition/retention (which has already merged) means that we can fall back to other devices gracefully, and now the pushed/pulled tracks can automatically reconnect if the peer connection is disrupted while React happily just updates things when new tracks/track metadata is emitted.

Fix dead track detection

Use RxJS for screensharing

Organize hooks a bit better

Fix bug in device selection menu

Update packet loss info
@third774 third774 merged commit d2c4d07 into main Jul 24, 2024
2 checks passed
@third774 third774 deleted the rxjs-for-rtcpeerconnection branch July 24, 2024 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants