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
Would it be possible to combine json-over-tcp with tls?
I have made a dirty solution for myself by replacing net.Server with tls.Server and the connection event with secureConnection but this breaks plain TCP
The text was updated successfully, but these errors were encountered:
Hmm, it wasn't designed with TLS in mind, but there's no reason why it can't be used with it.
The protocol.js file is the one that does the heavy lifting and it's abstracted to the level that it just cares about streams, it has no dependencies to the 'net' package.
Server.js and socket.js are simple wrappers on the 'net' package server and connection, so you could create similar wrappers for the 'tls' server and connection and wire them to protocol.js in a similar fashion. I haven't looked at the tls api, if it's derived off of the tcp api, it may be better to just abstract out server.js and socket.js to accept any object that conforms to that api instead of creating additional files. Let me know if you have any questions on how to go about doing that.
Looks like this project was done way back, but this issue #1 and project has inspired me with the Madtom implementation. See https://github.com/mauris/madtom
Would it be possible to combine json-over-tcp with tls?
I have made a dirty solution for myself by replacing
net.Server
withtls.Server
and theconnection
event withsecureConnection
but this breaks plain TCPThe text was updated successfully, but these errors were encountered: