Skip to content
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

Do not call teardown or async_teardown #3

Open
vinniefalco opened this issue Sep 24, 2018 · 1 comment
Open

Do not call teardown or async_teardown #3

vinniefalco opened this issue Sep 24, 2018 · 1 comment

Comments

@vinniefalco
Copy link

teardown and async_teardown are called automatically as part of the WebSocket close procedure, there is no need to invoke them manually:

// :TODO: we shoudl be using teardown? http://vinniefalco.github.io/beast/beast/ref/beast__websocket__async_teardown/overload2.html

If you implement your own socket class, and you want it to work with beast::websocket::stream then you will need to provide overloads of teardown and async_teardown which will be called as needed to perform the WebSocket close.

@NuSkooler
Copy link
Contributor

@vinniefalco Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants