Gitter API: Cancellation and Timeout Handling for HTTP 429 and WebSocket Heartbeats

Gitter API: Cancellation and Timeout Handling for HTTP 429 and WebSocket Heartbeats

The goal is to understand how Gitter’s client library manages cancellation of in‑flight HTTP requests and WebSocket messages when a timeout or rate‑limit occurs. The documented HTTP 429 response includes a Retry‑After header, but the client’s retry logic and whether it aborts the original request remain unclear. For WebSocket, a ping/pong heartbeat is used, yet the exact timeout threshold and the fate of queued messages after a timeout are not specified.

Key uncertainties:

• Does the client automatically retry after the Retry‑After interval, or must the caller manually re‑issue the request?
• When a WebSocket ping times out, are pending outgoing messages canceled or left pending until a reconnection?
• Is there a public cancel() or close() API that aborts pending HTTP requests without closing the socket?