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

Why should websocket be destroyed when getting LWS_CALLBACK_CLIENT_WRITEABLE? #5

Open
klauski opened this issue Jan 4, 2019 · 0 comments

Comments

@klauski
Copy link

klauski commented Jan 4, 2019

When socket become writeable, runtime error rises because web client go to be destroyed..

The related code is in scclient.cpp,
if (writeable_flag)
destroy_flag = 1; <= raise problem
}
break;
case LWS_CALLBACK_CLIENT_WRITEABLE :{
// printf(KYEL"[Main Service] On writeable is called. send byebye message\n"RESET_);
websocket_write_back(wsi, (char *)"Byebye! See you later", -1);
writeable_flag = 1;

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

1 participant