MoeraOrg / MoeraOrg/moera-issues
Message when WebSockets connection is broken
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
If WebSockets client fails to reconnect several times, deactivate the client and display message "Connection to node broken, reconnecting in ... sec [Reconnect]" (like in GMail). After the delay or if "Reconnect" is clicked, activate the client again. The delay should be increased on every retrial.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the WebSockets client and its reconnect handling. Verify the current retry behavior, then define the broken-connection message, increasing delay, manual Reconnect action, and client deactivation described here. Done means repeated failures show the message, retries back off, and either the delay or the action restores the client.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100