Dear team,

We have deployed our push service using a2 into production, but we are frequently observing ConnectionReset errors on http2 connections.

Our service is multi-tenant and the traffic is a steady stream of messages with idle periods and bursts in between.
Although we are working around these connection resets by retrying it. I was thinking if we could do something like sending periodic keep-alive messages over the open connection.

The pushy library already does something like this: jchambers/pushy#266

I read through the hyper documentation, and the default is to not send any keep-alives