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

RTCRtpReceiver instance #496

Closed
robin-raymond opened this Issue Apr 22, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@robin-raymond
Contributor

robin-raymond commented Apr 22, 2016

An RTCRtpReceiver instance is associated to a receiving MediaStreamTrack and provides RTC related methods to it.

This part:

is associated to a receiving MediaStreamTrack

... reads exactly like the sender. But I think it shouldn't as it's not associated like the sender but constructed by the receiver based upon the kind.

@robin-raymond robin-raymond added the 1.1 label Apr 22, 2016

@ibc

This comment has been minimized.

Show comment
Hide comment
@ibc

ibc Apr 22, 2016

Contributor

"An RTCRtpReceiver instance produces an associated receiving MediaStreamTrack and provides RTC related methods to it."

Contributor

ibc commented Apr 22, 2016

"An RTCRtpReceiver instance produces an associated receiving MediaStreamTrack and provides RTC related methods to it."

@robin-raymond

This comment has been minimized.

Show comment
Hide comment
@robin-raymond

robin-raymond Apr 22, 2016

Contributor

@ibc yes, that's better.

Contributor

robin-raymond commented Apr 22, 2016

@ibc yes, that's better.

@aboba

This comment has been minimized.

Show comment
Hide comment
@aboba

aboba Apr 22, 2016

Contributor

Agree.

Contributor

aboba commented Apr 22, 2016

Agree.

aboba added a commit that referenced this issue Apr 25, 2016

@aboba aboba added the PR exists label Apr 25, 2016

@robin-raymond

This comment has been minimized.

Show comment
Hide comment
@robin-raymond

robin-raymond Apr 25, 2016

Contributor

Better.

Contributor

robin-raymond commented Apr 25, 2016

Better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment