Skip to content
New issue

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

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

Already on GitHub? # to your account

Socket: discourage concurrent sends and concurrent receives #9216

Merged
merged 1 commit into from
Aug 25, 2023
Merged
Changes from all commits
Commits
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
6 changes: 5 additions & 1 deletion xml/System.Net.Sockets/Socket.xml
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,11 @@

]]></format>
</remarks>
<threadsafe>Instances of this class are thread safe.</threadsafe>
<threadsafe>
It is safe to perform a send and a receive operation simultaneously on a <see cref="T:System.Net.Sockets.Socket" /> instance,
but it's not recommended to issue multiple send or multiple receive calls concurrently. Depending on the underlying platform
implementation, this may lead to unintended data interleaving for large or multi-buffer sends or receives.
</threadsafe>
<altmember cref="N:System.Net" />
<altmember cref="N:System.Net.Cache" />
<altmember cref="N:System.Net.Security" />
Expand Down