Joey Eremondi on Nostr: Network question from a total noob, maybe will provide someone with some distraction. ...
Network question from a total noob, maybe will provide someone with some distraction. Boosts welcome.
Is there a general technique for turning a TCP based protocol into an HTTP/HTTPS based one, or writing a middle server to do this?
Basically, I've got the Racket handin server, which is currently written to open a TCP connection, send some text messages back and forth (protocol below), and then close the connection.
What I want is to be able to have it behind an nginx reverse proxy (that I don't control) that only forwards http/https to my server.
What's involved in converting the protocol to be over http so it can be behind the proxy? Is there a notion of "open connection" in Http, or is it just "send request, get response, close" over and over again?
Are there off-the-shelf solutions that go in between, so I would only have to alter the client and not the server?
Is there a general technique for turning a TCP based protocol into an HTTP/HTTPS based one, or writing a middle server to do this?
Basically, I've got the Racket handin server, which is currently written to open a TCP connection, send some text messages back and forth (protocol below), and then close the connection.
What I want is to be able to have it behind an nginx reverse proxy (that I don't control) that only forwards http/https to my server.
What's involved in converting the protocol to be over http so it can be behind the proxy? Is there a notion of "open connection" in Http, or is it just "send request, get response, close" over and over again?
Are there off-the-shelf solutions that go in between, so I would only have to alter the client and not the server?