Comment by mort96 2 years ago So we need a protocol with some kind of non-optional default-enabled keepalive. 2 comments mort96 Reply josefx 2 years ago Now your connections start to randomly fail in production because the implementation defaults to 20ms and your local tests never caught that. mort96 2 years ago I'm sure there's some middle ground between "never time out" and "time out after 20ms" that works reasonably well for most use cases
josefx 2 years ago Now your connections start to randomly fail in production because the implementation defaults to 20ms and your local tests never caught that. mort96 2 years ago I'm sure there's some middle ground between "never time out" and "time out after 20ms" that works reasonably well for most use cases
mort96 2 years ago I'm sure there's some middle ground between "never time out" and "time out after 20ms" that works reasonably well for most use cases
Now your connections start to randomly fail in production because the implementation defaults to 20ms and your local tests never caught that.
I'm sure there's some middle ground between "never time out" and "time out after 20ms" that works reasonably well for most use cases