Skip to content
This repository has been archived by the owner on Feb 24, 2023. It is now read-only.

Normalize reconnectTimeWait and maxReconnectAttempts #72

Closed
aricart opened this issue Feb 12, 2020 · 0 comments · Fixed by #75
Closed

Normalize reconnectTimeWait and maxReconnectAttempts #72

aricart opened this issue Feb 12, 2020 · 0 comments · Fixed by #75

Comments

@aricart
Copy link
Member

aricart commented Feb 12, 2020

Current behavior is to wait reconnectTimeWait for any reconnect. It should be on a per-server basis based on the last connect time. Similarly, maxReconnectAttempts is not per-server but an actual count of retries.

aricart added a commit that referenced this issue Feb 13, 2020
… match other clients.

Enhanced the `timeout`, to take into account not only the dial portion of the connection, but also all the way until the first PONG is processed.
aricart added a commit that referenced this issue Feb 14, 2020
Reworks timeout to account not only for dial, but also for completion of the connection protocol.
@aricart aricart mentioned this issue Feb 14, 2020
aricart added a commit that referenced this issue Feb 14, 2020
- FIX #72 - `reconnectTimeWait`, `maxReconnectAttempts`
- Reworks timeout to account not only for the dial, but also for the completion of the connection protocol.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant