-
Notifications
You must be signed in to change notification settings - Fork 636
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.
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
Clarify documentation on stream thread safety #329
Labels
Doc
A documentation specific issue
Comments
vinniefalco
added a commit
that referenced
this issue
Apr 28, 2017
vinniefalco
added a commit
that referenced
this issue
Apr 28, 2017
vinniefalco
added a commit
that referenced
this issue
Apr 28, 2017
vinniefalco
added a commit
that referenced
this issue
Apr 28, 2017
vinniefalco
added a commit
that referenced
this issue
Apr 28, 2017
vinniefalco
added a commit
that referenced
this issue
May 1, 2017
vinniefalco
added a commit
that referenced
this issue
May 1, 2017
vinniefalco
added a commit
that referenced
this issue
May 5, 2017
vinniefalco
added a commit
that referenced
this issue
May 5, 2017
vinniefalco
added a commit
that referenced
this issue
Jul 20, 2017
vinniefalco
added a commit
that referenced
this issue
Jul 20, 2017
vinniefalco
added a commit
that referenced
this issue
Jul 23, 2017
madmongo1
added a commit
to madmongo1/beast
that referenced
this issue
Mar 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
websocket::stream
docs should state:Thread Safety
Distinct objects: Safe.
Shared objects: Unsafe.
This applies to both the synchronous and asynchronous interfaces.
The text was updated successfully, but these errors were encountered: