Use sdp-interop
#19
Open
Use sdp-interop
#19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Well, does it enable interoperability? If not, then let's not do this. Maybe this functionality needs to go into our own SDP munging module https://github.com/rtc-io/rtc-sdp ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is more of a request for comment than a serious PR
Uses the
sdp-interopmodule from Jitsi to provide some greater multi stream interoperability between Chrome and Firefox. I'm not necessarily sold on this in it's current state, as it doesn't seem to provide any real benefits to the use cases I'm trying with, but I though I'd throw it out there for wider thoughts.Requires the changes from https://github.com/jitsi/sdp-interop/compare/issue-13 to be applied to
sdp-interopif you are using data channels.