Nov 16, 2019 10:49 PM|mgebhard|LINK
I made a test and if i do not insert that function inside a Task.Run, if i receive a response from a service while another previous parse is still in progress, the current does not start until the previuos finish. So the whole procedure is slower. Is there
another way to avoid that "block" ?
The processing is not any faster. The Run.Task() spins up a new thread which execute the ParseContent() sub. This allows the CallSupplier() function to return without a response.
If you do not care about the response then do not await the CallSupplier() function. Your current approach wastes a thread which the async/await pattern is designed to save.