-
Notifications
You must be signed in to change notification settings - Fork 31
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
[Improvement] More simple samples on separate Client-Server apps #7
Comments
Btw, there is a long-standing TODO to migrate chat sample to optional secure sockets w/ |
I see, thanks. However, what if the main thread busy with some time-consuming operation, let's say 1 sec (or some amount of time > timeout), and during this time net packet is incoming? Does user control version have a benefit in such case? I didn't test yet this case, though. |
When main UI thread is busy no socket events can be received on this main UI thread so communication is paused until main thread can pump messages (becomes available) again. There is no difference in this behavior between MS Winsock controll, cAsyncSocket class and ctxWinsock replacement control. |
Updated GET samples. Remains to do a fix for HTTPS to make it work... |
In The |
Project added under 10x! |
Suggestion:
to have more minimalistic samples. Projects attached.
Winsock-simple.zip
Also, don't you mind to clarify:
Thank you.
The text was updated successfully, but these errors were encountered: