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

Unix transport #16

Open
mcollina opened this issue Jul 30, 2014 · 3 comments
Open

Unix transport #16

mcollina opened this issue Jul 30, 2014 · 3 comments

Comments

@mcollina
Copy link
Contributor

Let's first let the libchan guys how they want to roll out that in libchan.

@AdrianRossouw
Copy link
Contributor

so i'm assuming, given their stance on websockets, they would just want to run SPDY over the socket directly.

If node-spdy has node's net and http modules ingrained in it's heritage, it should mean that specifying a filename instead of a port should just work, no ? At least for the server.

On the client, you would have to check that it allows you specify the socketPath when making a new spdy connection (in http, this is done by specifying socketPath to http.request)

@mcollina
Copy link
Contributor Author

No. The whole point is that they can send file descriptors directly, so
transferring files is super-fast.

Here we wait them.

@AdrianRossouw
Copy link
Contributor

i'm guessing something like the websocket stream would work for this now, since we aren't waiting on the libchan guys anymore and we are just using websockets as a dumb pipe.

will write up a test for just net.listen()

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

2 participants