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

RTCQuicStream: basic interface definition (readInto, write, close, on… #786

Merged
merged 5 commits into from
Oct 23, 2017

Conversation

aboba
Copy link
Contributor

@aboba aboba commented Oct 18, 2017

Adds a portion of the RTCQuicStream interface: readInto, write, close, onstatechange.

Edits can be viewed here.

Rebase of PR #785

…statechange)

Adds a portion of the RTCQuicStream interface: readInto, write, close, onstatechange.

Edits can be viewed [here](http://internaut.com:8080/~baboba/ortc/github/quic-master/#quicstream*).

Rebase of PR #785
@aboba aboba added the 1.1 label Oct 18, 2017
Copy link

@pthatcherg pthatcherg left a comment

Choose a reason for hiding this comment

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

LGTM

@aboba
Copy link
Contributor Author

aboba commented Oct 20, 2017

@robin-raymond @pthatcherg Can you do a final review?

@lgrahl
Copy link
Contributor

lgrahl commented Oct 20, 2017

I'm wondering how readInto is supposed to work: Is it intended to be polled? Is it blocking (unlikely, but still)? Does it return all currently available data or the whole stream's data? If it doesn't block, how would I know that there is data available (as there's neither an event nor a Promise)?

What about the discussion in #785?

@aboba
Copy link
Contributor Author

aboba commented Oct 23, 2017

@lgrahl Good questions. We still need to figure out how the buffering model works. But the intent is to add that in a subsequent PR.

@aboba aboba merged commit 00c2d4e into master Oct 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants