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

node-spdy #4

Closed
pelger opened this issue Jul 10, 2014 · 6 comments
Closed

node-spdy #4

pelger opened this issue Jul 10, 2014 · 6 comments
Assignees

Comments

@pelger
Copy link
Contributor

pelger commented Jul 10, 2014

Research and send a feedback email to this list about node-spdy

@mcollina
Copy link
Contributor

I investigated how libchan uses SPDY for sending streams, and I'm pretty confident I can replicate that easily with node-spdy once we have a target API.

libchan uses SPDY stream identifiers to send nested channels, e.g. when the client receives a stream pushed stream from the server, it can now the parent request via the SPDY stream identifier. The only catch is that it requires some gymnastic to keep track of all those identifiers, just how libchan does. However, node-spdy does this for us for free, we just need to stick a reference to our message into the connection. Have a look at https://github.com/GraftJS/jschan/blob/master/test/spdy-demo.js#L35. So, we can have nested channels in node.js too!

I'm eager to have #6 defined, so I can start coding this 🎯.

@AdrianRossouw
Copy link
Contributor

totally awesome!

I'm gonna riff on usage.md now then.

@mcollina mcollina mentioned this issue Jul 15, 2014
@mcollina
Copy link
Contributor

libchan people are changing their interface to not rely on SPDY stream identifiers, but to pass libchan identifiers through headers.
It's more complex than what I thought :(

docker/libchan#38

@AdrianRossouw
Copy link
Contributor

Have you asked on IRC? #libswarm on freenode.

It is possible that you can connect to a previous revision of the library? Have we got abstractions enough to handle the various types they talk about there?

@mcollina
Copy link
Contributor

I would say they are planning to break backward-compatibility. I'll ask on IRC.

@mcollina
Copy link
Contributor

Closing for the discussione we had, it's doable :).

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

No branches or pull requests

3 participants