I have a class with an event-based asynchronous operation (EAP). I can make an action based on that as it is described.
When I EAP:
My Thread - & gt; Call method - & gt; Which makes threads - & gt; In which it does something
When I work I suspect that:
my thread -> gt; Creates a task - & gt; Creates a Thread - & gt; Which method calls - & gt; Which makes threads - & gt; Edit: Offcourse will not create a thread - this thread will take thread from the pool if needed. But will it be taken and will I have to spend valuable extra threads from the thread pool? OK to know what's going to happen, I'll need to see your specific code, In which you will use the If you want to know what will happen if you have used But will continuity take a new thread from the pool or is it the thread taken from the pool What matters is that no thread will be blocked until the operation is complete or not. And in both cases, this is not going to happen. task as a result. But in general if you use EAP by using
work
task end source , this will not use another thread from the pool because there is no code to be executed.
continue on that
task , then it depends on whether you set Whether or not you do not set it, then continuity will be a new thing. The thread taken from the pool if you set it, then it runs on the same thread that sets the result of
task . (You should use
Execute Synchronous to keep very little current.)
Comments
Post a Comment