3 ms·
Fair enough :) If I were to run a container that handled tcp connections, is there any sort of max connection duration? One of the projects I have worked on i
by justinsaccount 6y ago
Fair enough :)
If I were to run a container that handled tcp connections, is there any sort of max connection duration?
One of the projects I have worked on involved accepting tcp connections from cellular connected race timing boxes, dealing with their protocol and sending the resulting data into another system.
I guess you could think along the lines of syslog or MQTT.
This isn't very bandwidth or CPU intensive, but does require keeping the sockets open for hours at a time.
- tptacek 6y agoThis has come up before! If you like, you can hit me up at thomas@fly.io and I can take a whack at telling you how well this'll work out-of-the-box. What I can say is that "ordinary" TCP connections at Fly run through our Anycast proxy infrastructure, which does expect that it can bounce connections whenever it needs to --- but we can route around that for long-term connections, which is a thing that people doing, for instance, WebRTC want.
- justinsaccount 6y agoCool! With covid I haven't had the chance to work on any races lately, so I don't have an immediate need for this right now. heroku/app engine/lambda/cloud run all replace CGI in one way or another, but none of them can replace inetd.