B
Bob Rock
Hello,
exploring more and more the .NET framework I've seen that threads are
often employed by the framework, for example in:
- callback methods on timers
- async operations (async receives on message queues, etc.)
Wanting to avoid executing the event handler code in a different
thread is there a *standard* way (something like a pattern) to
accomplishing this??? I remember having read something relative to the
need to update UIs only from the thread that creates them. Having a
worker thread that needs to update a UI element how can the update be
done by the thread that created the UI on behalf of the worker
thread??? I'm asking because I believe that the same approach could be
a possible answer to my initial question.
Thx.
Bob Rock
exploring more and more the .NET framework I've seen that threads are
often employed by the framework, for example in:
- callback methods on timers
- async operations (async receives on message queues, etc.)
Wanting to avoid executing the event handler code in a different
thread is there a *standard* way (something like a pattern) to
accomplishing this??? I remember having read something relative to the
need to update UIs only from the thread that creates them. Having a
worker thread that needs to update a UI element how can the update be
done by the thread that created the UI on behalf of the worker
thread??? I'm asking because I believe that the same approach could be
a possible answer to my initial question.
Thx.
Bob Rock