This repository was archived by the owner on Feb 26, 2021. It is now read-only.
Migration to Pull Streams - Experiment C #21
Closed
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.
Mode C
This is one of the experiments done in order to test the migration to pull-streams, with regards to stream muxing.
Mode B consists in having pull streams exposed from the spdy stream muxer, while layering spdy on top of Node.js Streams, that are layered on pull-streams, that are layered on Node.js streams. This experiment was created because it represents most of the real scenarios, where we have Node.js streams from the transports and have to convert them to pull-streams for the connection upgrades, secio, etc, but for spdy, we need to convert it back. The problems that this solution presents match the same problems in Mode A.
Illustration:

Notes
How to test it yourself
In order to test this, you need to have to have the
pull-streams
migration ofinterface-connection
available in your local env. Here are the steps