Skip to content

Improve Reconnecting WS Configurability #525

Closed

Description

@Archmonger

Current Situation

Currently the configuration for reconnecting WS is fairly limited.

Proposed Changes

We can potentially add settings for MAX_TIMEOUT , MAX_RETRIES, and/or RECONNECT_INTERVAL.

Alternatively, allow the user to define his own JavaScript WS reconnection function.

Implementation Details

From @rmorshea
I'd actually like to modify how reconnections happen so its more configurable. It should accept a callback that receives the last delay, and the total elapsed time as its arguments and returns the next delay.

It should probably be even a bit more general in that, there should be a way to hook into the full lifecycle of the connection:

  • before initial connection
  • connected
  • disconnected
  • closed
  • etc...

Activity

  1. added this to the milestone on Jan 11, 2022
  2. modified the milestones: , on Jan 29, 2023
  3. removed this from the milestone on Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority-2-moderateShould be resolved on a reasonable timeline.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions