[{"author": "Reese Enghardt", "text": "
Stepping out for a few minutes, brb
", "time": "2023-10-17T15:08:46Z"}, {"author": "Reese Enghardt", "text": "back
", "time": "2023-10-17T15:15:08Z"}, {"author": "Devon O'Dell", "text": "kebab-case-is-like-this
", "time": "2023-10-17T15:17:35Z"}, {"author": "Brian Trammell", "text": "til
", "time": "2023-10-17T15:37:56Z"}, {"author": "Devon O'Dell", "text": "Looking at For keepAliveTimeout is tickling something that maybe needs a different discussion. If I have a higher-level protocol (like h2) that has its own keepalive protocol, and is built on top of a protocol like TCP which has an idea of keepalive, should I expect keepalive to be enabled on all protocols?
", "time": "2023-10-17T15:44:54Z"}, {"author": "Devon O'Dell", "text": "(Is keepaliveTimeout enough to allow specifying TCP keepalive behavior? This typically also has a keepalive count as well.)
", "time": "2023-10-17T15:47:49Z"}, {"author": "Brian Trammell", "text": "horn practice time
", "time": "2023-10-17T16:23:59Z"}, {"author": "Brian Trammell", "text": "giant shrug
", "time": "2023-10-17T16:29:32Z"}, {"author": "Reese Enghardt", "text": "I have to head out to another meeting. Thanks everyone, and see some of you in Prague!
", "time": "2023-10-17T16:59:51Z"}, {"author": "Devon O'Dell", "text": "take care all
", "time": "2023-10-17T17:00:29Z"}]