-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
pion/webrtc@v4 Release #2557
Comments
Not needed but may be good to address #2292 |
Maybe we can revert this revert as networkType is not "tcp4"/"tcp6"/etc according to the webrtc-stats? |
Also, I find very confusing that we have even though getter is more accurate: I suggest it is worth making more consistent |
@aalekseevx Do you mean to do polling instead of event callback? |
@aalekseevx nice catch! I will make both changes |
Return ICEGatheringState not ICEGathererState Relates to #2557
Return ICEGatheringState not ICEGathererState Relates to #2557
Return ICEGatheringState not ICEGathererState Relates to #2557
Return ICEGatheringState not ICEGathererState Relates to #2557
Better to remove deprecated things |
Created v4 milestone to track the issues/PRs targeting v4 |
Using slog sounds good, but slog config should be configurable via |
I'm onboard with that. Also love using zap |
Found a performance regression in SampleBuilder: #2778 |
I merged a breaking change with 60eea43
This added support for DTLS Close Notify. This means the PeerConnection will transition to
Closed
directly without user interaction. Pion's documentation only suggested handlingFailed
andDisconnected
before. Users will need to manually audit their code before upgrading.Since we are breaking the API does anyone else things that are worth changing?
Changes
Complete
TODO
pion/interceptor
pion/rtcp
pion/rtp
pion/sctp
pion/srtp
pion/turn
The text was updated successfully, but these errors were encountered: