Skip to content

Document .NET 11 Happy Eyeballs considerations for future C# WebSocket clients #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Codex wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Document .NET 11 Happy Eyeballs considerations for future C# WebSocket clients #5

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5899d4e
Initial plan
Codex Feb 13, 2026
0eda42a
docs: note dotnet happy eyeballs considerations
Codex Feb 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/architecture/ARCHITECTURE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -476,6 +476,11 @@ Client Server
- Resume from last checkpoint
- Pending operations buffered in offline queue

**IPv4/IPv6 Dialing (Happy Eyeballs):**
- .NET 11 preview adds `ConnectAlgorithm.Parallel` to `Socket.ConnectAsync`, enabling Happy Eyeballs (RFC 8305) for WebSocket/TCP dials ([release notes](https://github.com/dotnet/core/blob/main/release-notes/11.0/preview/preview1/libraries.md#happy-eyeballs-support-in-socketconnectasync)).
- SyncKit does not ship a .NET/WebSocket client today, so there is no immediate code change.
- If a C# client is added later, target .NET 11+ and opt into `ConnectAlgorithm.Parallel` (or equivalent) to avoid IPv6-only stall/regression risks when connecting to the WebSocket server.

---

## Conflict Resolution
Expand Down