More advanced socket extension usage for Windows
Open
Nobody has claimed this yet.
Feature
OS: Windows
Status: Needs Triage
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
Mostly asking @cmb69 opinion about this. Some advanced features cannot be set via setsockopt but via Winsock API (i.e. WinIOCtl) e.g. delayed ACK ; but then we might enter in a world of hurts with the Winsock mandatory initialisation (per DLL ?). Is it worth it you think ?
Contributor guide
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
No file, test, or entry point is named. Start by locating the Windows socket extension and its Winsock initialization; clarify whether supporting WinSock APIs such as WinIOCtl is desired and what specific behavior would define completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100