Re:Show HN: Inlets 2.0 – expose your local endpoints to the ...
by ComputerGuru on Thursday July 11, 2019 @09:10AM
(#20411198)
That issue was not handled in a way that makes it an open source project I’d want to contribute to.
Re:Show HN: Inlets 2.0 – expose your local endpoints to the ...
by icebraining on Thursday July 11, 2019 @09:36AM
(#20411383)
How would you prefer it be handled?
I'm a bit curious about the choice of websockets as a protocol over the tunnel, though. Why is "tunnelling plain (non-HTTP) traffic over TCP" a non-goal? What's the benefit over just tunneling the HTTP traffic over a reverse SSH tunnel or similar?
EDIT: Maybe it's just a question of the author finding websockets "good enough" (despite performance overhead) and wanting to keep the scope small with a single implementation that isn't really going anywhere. Here a suggestion on using WebRTC instead of Websockets: https://github.com/alexellis/inlets/issues/49
> Thanks for the suggestion. I'll look into webrtc when I get time, but for the time-being I think web sockets are going to be the way inlets works.