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

fix: Rename webrtc-w3c to webrtc and webrtc to webrtc+sdp-munging #153

Closed
wants to merge 1 commit into from

Conversation

achingbrain
Copy link
Member

Summary

Following on from #150 and an replacement for #151

Renames:

  • /webrtc-w3c -> /webrtc - AKA browser to browser
  • /webrtc -> /webrtc+sdp-munging - AKA browser to server

Discussion:

Before Merge

Following on from #150 and an replacement for #151

Renames:

- `/webrtc-w3c` -> `/webrtc` - AKA browser to browser
- `/webrtc` -> `/webrtc+sdp-munging` - AKA browser to server

Discussion:

- This option comes from comments on #151
- It got a lukewarm reception on the triage call so it's presented as an option along with #152
- Adding `+sdp-munging` makes it more explicit about the differences, though admittedly there are other differences that aren't encapsulated in the name
- People were uncertain about universal understanding of the term "SDP munging"
Copy link
Contributor

@thomaseizinger thomaseizinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we are making a breaking change, I am in favor of this one.

@@ -35,7 +35,7 @@ code, size, name, comment
277, 0, p2p-stardust,
275, 0, p2p-webrtc-star,
276, 0, p2p-webrtc-direct,
280, 0, webrtc, ICE-lite webrtc transport
281, 0, webrtc-w3c, webrtc transport where connection establishment is according to w3c spec
280, 0, webrtc+sdp-munging, ICE-lite webrtc transport with SDP munging during connection establishment and without use of a STUN server
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
280, 0, webrtc+sdp-munging, ICE-lite webrtc transport with SDP munging during connection establishment and without use of a STUN server
280, 0, webrtc-with-sdp-munging, ICE-lite webrtc transport with SDP munging during connection establishment and without use of a STUN server

AFAIK, we don't need to save chars for performance reasons so this is perhaps a tad easier to understand?

@achingbrain
Copy link
Member Author

Closing in favour of #152

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