-
Notifications
You must be signed in to change notification settings - Fork 683
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
HTTP/2-based provider protocol #278
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
Most of this was untested. Some tests have been disabled as they directly relate to the old protocol. Next step is to selectively refactor them around HTTP/2. There's no docs yet so I'm basing this on the info in Session 720 at WWDC'15
I don't know why Sublime didnt format it this way
In the new protocol it would seem that there is no special distinction for VoIP payloads. Everything is the same length.
With the new protocol there should be no need to resend notifications as the connection remains open in the event of any errors.
With HTTP/2 it should only be necessary to keep one connection open as there will be no frequent reconnects to slow things down. If multiple are needed then the behaviour can be reintroduced after the basics are working.
node-http2 requires streams, anything less than 0.10 won't do
FYI: Any ETA as to when we can expect a first version that supports it? :) |
Bluebird is generally considered to be the most performant promises library available
It's tidier than importing each function individually.
Otherwise endpointManager might not continue sending
I guess I know why I use Transform not PassThrough now.
It's unnecessary complexity...
1 similar comment
2 similar comments
Ensure it's not stretched and lighten the text a little. Also centre again because it looks nicer now
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.
In WWDC15 Session 720, a new provider protocol was introducted based on HTTP/2. This branch will implement the new support.
shutdown
I will move this work to separate PR's
Fixes #362, #277, #240, #168