localsend / localsend/protocol
Add fallback port
Nobody has claimed this yet.
- Dominant language
- Mermaid
- Stars
- 571
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
The current default is to use port 53317, however, there is a small probability that this port is used as "ephemeral port". (See https://github.com/localsend/localsend/issues/125)
A solution for this is to add a fallback port if 53317 is already occupied.
The fallback port should be a lower-number port which will be upgraded to default in another future release.
I really liked your way of thinking @Jipok. What do you think ? Do you know of any good port?
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
Review the protocol's current handling of default port 53317 and the referenced LocalSend issue 125 first. Define a lower fallback port and verify behavior when 53317 is occupied; the issue is done when that fallback is specified and implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100