This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
Interop requirement - spdy / http2 #16
Labels
topic/libp2p
Topic libp2p
Comments
does the spdystream implementation by docker even interop correctly with one of the node implementations? I feel like that would be a good thing to test before we go much farther down that road. |
For logging purposes: It was discussed and reviewed again and As for the spdystream implementation in Node.js, had a quick chat today with Indutny on IRC:
The refactor should take about 2 weeks (ref: spdy-http2/node-spdy#208) |
We have it now :) |
Which version of SPDY is ipfs using? The wikipedia says that the latest version is version 4.0. |
We use 3.1 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Opening this discussion on a issue, so that we have a log, as it has been a recurring topic for a while now :)
For interop purposes between implementations, it has been discussed several times to replace
yamux
forspdy
, so other implementations can have access to a standard stream multiplexing library. However, most implementations for spdy or http2 are not there yet and pretty much every single one of them doesn't offer a streamable io interface, with the exception ofspdystream
by Docker, however, @whyrusleeping and @jbenet found some deadlock scenarios that still need to be solved/merged by the Docker team.So, I guess we have to figure out if http2/spdy is the way and if so, will we invest resources on making our own implementation/supporting a current open source one?
The text was updated successfully, but these errors were encountered: