So what is sendbuffersize supposed to do? seems like its just thrown away

Open
#98,527 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Start with ClientWebSocketOptions.cs at the linked line and trace where sendbuffersize is stored and consumed in the WebSocket client implementation. Compare the relevant transport paths to determine the intended behavior; done means the option is either correctly honored with regression coverage or its supported behavior is clearly established.

Written by the indexing model from the issue text.

Description

area-System.Net documentation

https://github.com/dotnet/runtime/blob/8cb1f79fd66850e233a4b756aa0b5407e64f1105/src/libraries/System.Net.WebSockets.Client/src/System/Net/WebSockets/ClientWebSocketOptions.cs#L214C36-L214C37

Dominant language
C#
Stars
18.3k
Forks
5.6k
Avg merge
2d 19h
Merged PRs (30d)
589

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.