[PR #252] [CLOSED] changed reconnect from milliseconds to seconds, improved reconnect attempt #1062

Closed
opened 2026-02-27 15:52:58 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/quasar/Quasar/pull/252
Author: @ghost
Created: 6/1/2015
Status: Closed

Base: masterHead: seconds


📝 Commits (1)

  • 3c27b4a changed reconnect delay from milliseconds to seconds, improved randomness in reconnect attempt

📊 Changes

3 files changed (+17 additions, -14 deletions)

View changed files

📝 Client/Config/Settings.cs (+2 -2)
📝 Client/Program.cs (+4 -1)
📝 Server/Forms/FrmBuilder.Designer.cs (+11 -11)

📄 Description

I changed the reconnect delay from milliseconds to seconds. The builder form label changed to "seconds" and the client now multiplies the reconnect delay by 1000 to convert it to milliseconds. I modified the defaults for debug to be 1 second and for production to be 300 seconds, or 5 minutes. The previous value of 5 seconds created a much too obvious rapidly polling outgoing connection.

Additionally I modified the randomness in the reconnect timeout to always be between 50% and 150% of the configured value, allowing for a better randomly staggered reconnect time that is less likely to show up as a simple recurring pattern. If you use the 5 minute default that I set then the retry time will be between 2.5 minutes and 7.5 minutes.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/quasar/Quasar/pull/252 **Author:** [@ghost](https://github.com/ghost) **Created:** 6/1/2015 **Status:** ❌ Closed **Base:** `master` ← **Head:** `seconds` --- ### 📝 Commits (1) - [`3c27b4a`](https://github.com/quasar/Quasar/commit/3c27b4a65e1f2d26cc2c6e3a7bba443b61549f1d) changed reconnect delay from milliseconds to seconds, improved randomness in reconnect attempt ### 📊 Changes **3 files changed** (+17 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `Client/Config/Settings.cs` (+2 -2) 📝 `Client/Program.cs` (+4 -1) 📝 `Server/Forms/FrmBuilder.Designer.cs` (+11 -11) </details> ### 📄 Description I changed the reconnect delay from milliseconds to seconds. The builder form label changed to "seconds" and the client now multiplies the reconnect delay by 1000 to convert it to milliseconds. I modified the defaults for debug to be 1 second and for production to be 300 seconds, or 5 minutes. The previous value of 5 seconds created a much too obvious rapidly polling outgoing connection. Additionally I modified the randomness in the reconnect timeout to always be between 50% and 150% of the configured value, allowing for a better randomly staggered reconnect time that is less likely to show up as a simple recurring pattern. If you use the 5 minute default that I set then the retry time will be between 2.5 minutes and 7.5 minutes. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-27 15:52:58 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#1062
No description provided.