> I share this opinion.
> I would let the client sockets attached to a single the thread (no
necessarily the main thread) and handle all communication. Once a job has
been received, then the data is passed to a worker thread, thru a queue, for
processing. Probably a single queue serviced by a pool of thread is enough.
What are your thoughts in having all communication in a single thread? In my
application we are starting to face some bottlenecks because all processing
of incomming data is received by the main thread, what we did was to change
the handle of some connections by detaching from main thread and attaching
to another thread to process the messages. The connections that we did that
are the ones that were causing the bottleneck.

So, my question is, in order to ICS to scale better in a multi-core machine
we should process the incoming Windows messages in different threads (Of
course, in a VERY WELL designed architecture to avoid deadlocks and
conflics) right?


To unsubscribe or change your settings for TWSocket mailing list
please goto
Visit our website at

Reply via email to