S
Sidanalism
I miss the old way when asynchronous calls are driven my window messages.
Yes a thread pool might greatly improve application performance but there
are time I don't want my event to be fire in a thread differ from the
calling thread. When a delegate is called in another thread it could be
frustrating for I have to consider thread occurrence issues in all the codes
it may invoke along my event chain. Sure the "Control.BeginInvoke()" could
be a work around but it is not always a good solution for I have to create
and initialize a Control object in my main thread and shared for all other
classes.
Is there any way my "OnReceive()" TCP message handler to be called
aschronously in my main thread by default ??
Thanks in advance!
Yes a thread pool might greatly improve application performance but there
are time I don't want my event to be fire in a thread differ from the
calling thread. When a delegate is called in another thread it could be
frustrating for I have to consider thread occurrence issues in all the codes
it may invoke along my event chain. Sure the "Control.BeginInvoke()" could
be a work around but it is not always a good solution for I have to create
and initialize a Control object in my main thread and shared for all other
classes.
Is there any way my "OnReceive()" TCP message handler to be called
aschronously in my main thread by default ??
Thanks in advance!