Keep-Alive timeouts #34

Activity

1. lovelydinosaur commented on Jul 23, 2019

   

   lovelydinosaur

   on Jul 23, 2019

   MemberAuthor

   More actions

   Actually I don't have any issue with the behavior that our ConnectionPool currently has. (let the connection expire on the server, limit number of connections and close above that limit)

   I think we will likely want to later round that out with a timeout value too, but it doesn't seem strictly required, and I think we can close this off as "currently out of scope".
2. lovelydinosaur

   closed this as completedon Jul 23, 2019
3. lovelydinosaur

   reopened this on Dec 11, 2019
4. lovelydinosaur commented on Dec 11, 2019

   

   lovelydinosaur

   on Dec 11, 2019

   MemberAuthor

   More actions

   Actually for robustness, this really is required.

   • asyncio has futzy connected-ness testing. Failing to detect lost connections (asyncio only) #95
   • If a server sends a 408 timeout response, then we'll still be connected. Handle 408-response connection closes. #146

   👍React with 👍1Reacted by Florimond Manca
5. lovelydinosaur

   added

   enhancementNew feature or requestNew feature or request

   on Dec 12, 2019
6. lovelydinosaur

   closed this as completedin #627on Dec 12, 2019