transports can be null #666
Merged
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
RTCRtpSender.transport and RTCRtpReceiver.transport can be null since the DTLS transports only come into existence after calls to setLocalDescription() and setRemoteDescription(). Still work-in-progress (do not merge yet). Related to Issue #651
Add text to clarify
More clarifications
More updates
|
@taylor-b Can you review? |
|
lgtm |
Add text about RTCIceTransport construction and remove text relating to destruction of RTCDtlsTransport objects.
Delete DTLS transport construction text
Remove DTLS transport text
|
lgtm |
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.
RTCRtpSender.transport and RTCRtpReceiver.transport can be null since the DTLS transports only come into existence after calls to setLocalDescription() and setRemoteDescription().
Related to Issue #651