getlantern / getlantern/unbounded
How should netstate handle half open connections and clearing the global state?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 57
- Forks
- 1
- Avg merge
- 20h 26m
- Merged PRs (30d)
- 13
Description
netstate was designed to test and observe the formal properties of discovery and matchmaking, not to test what happens when clients misbehave. So if you abruptly disconnect a client without cleaning up your state, netstated leaks your state.
If we want to mutate netstate into a backend for visualizing the global network on www.lantern.io, we need to figure out how to clean up state for clients who rudely depart.
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 examining the netstate and netstated state-handling paths mentioned in the issue, focusing on what remains after an abrupt client disconnect. Define the cleanup behavior needed for half-open connections and global state before attempting an implementation. Done means the expected handling of clients that depart without cleanup is agreed and documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100