Hacker News new | past | comments | ask | show | jobs | submit login

So we need a protocol with some kind of non-optional default-enabled keepalive.



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




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: