Uh oh!
There was an error while loading. Please reload this page.
Consistent stream semantics and forward compatibility with upcoming Stream v1.0 - #90
Merged
Merged
Conversation
Accordingly, the `drain` event now behaves consistently and we no longer need the custom `headers-written` event.
jsor
approved these changes
May 19, 2017
WyriHaximus
approved these changes
May 19, 2017
Fneufneu
commented
Jun 16, 2017
I'm a bit late but you forget to update README. $response->on('data', function ($data, $response) {should be $response->on('data', function ($data) { |
WyriHaximus
commented
Jun 16, 2017
Member
Feel free to open a PR fixing this 👍 |
clue
commented
Jun 16, 2017
MemberAuthor
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The
Requestis aWritableStreamInterfaceand now obeys its method and event semantics.The
Responseis aReadableStreamInterfaceand now obeys its method and event semantics.Resolves / closes#70
Supersedes / closes#83
Builds on top of / closes#87 (thanks @maciejmrozinski!)