This repository was archived by the owner on Jul 20, 2024. It is now read-only.
Is that __on_connection() thread only print the connection information and does not handle the connection as a separete thread #16
dungdamquoc1993
started this conversation in
General
Replies: 1 comment
-
I tried this before and it just turned out to be very inefficient and not scalable. Since we are only ever interacting with one client at a time, having a thread for each connevtion is pointless. The 2 seperate threads that exist now to handle incoming connections are to seperate API calls and GUI. basically you should be able to call methods to interact with a connection without being forced to print stuff out to the terminal on connection. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As I saw on this program there is 3 thread
main thread
_accept thread (listening for incoming connection)
__on_connection (only use for print connection)
and the connections are not executed in separate threads is that right?
Why shouldn't we create new thread for each connection
Beta Was this translation helpful? Give feedback.
All reactions