You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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.
Let's first let the libchan guys how they want to roll out that in libchan.
The text was updated successfully, but these errors were encountered: