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

Switch from bytes_to_send to send returning bytes #98

Merged
merged 2 commits into from
Jan 14, 2019

Conversation

pgjones
Copy link
Member

@pgjones pgjones commented Jan 13, 2019

This implements the ideas in #91.

This allows the outgoing_data buffer to be removed and instead left to the user to be concerned/deal with. This makes it very clear when wsproto has bytes to send (when send is called), and hence further clarifies the API. It also matches h11 expectations.

This is to avoid a blockquote concating these intentionally separate
and indented lines.
This allows the outgoing_data buffer to be removed and instead left to
the user to be concerned/deal with. This makes it very clear when
wsproto has bytes to send (when ``send`` is called), and hence further
clarifies the API. It also matches h11 expectations.
@pgjones pgjones merged commit fa70960 into python-hyper:master Jan 14, 2019
@pgjones
Copy link
Member Author

pgjones commented Jan 14, 2019

Thanks

@njsmith
Copy link
Member

njsmith commented Jan 14, 2019

It looks like this doesn't actually document .response() or when you need to call it in the main manual?

@pgjones
Copy link
Member Author

pgjones commented Jan 15, 2019

It doesn't, I've a proposal for HTTP/2 support I'd like to complete (and hopefully merge) then I plan to rewrite the documentation and examples.

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.

3 participants