Persistent connections
Registered by
Martin von Gagern
There should be an option to automatically reestablish lost connections.
There are two possible approaches for this:
1. Have a loop and ensure that every connection loss eventually returns to that loop, leaving the application in a sane state. This requires avoiding memory leaks as well as returning through many call levels in an exception-like way.
2. Have two separate processes, one running the loop and forking off the other. This would require more expressive exit codes and passing of signals to the child.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Martin von Gagern
- Direction:
- Needs approval
- Assignee:
- Martin von Gagern
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- Martin von Gagern
- Completed by
Related bugs
Sprints
Whiteboard
There is some work for approach 1 in the "persist-loop" branch. Returning to the loop on errors other than dead peer seems difficult, and memory leaks are a problem as well, so at the moment approach 2 seems more robust.
(?)
