A method that fetches an HTTP response and parses it involves two related tasks: the HTTP task carries the response text, while the method's task represents the full work through parsing. Keeping those responsibilities separate makes it easier to see which result, failure, or cancellation reaches the caller.
await lets a method yield while an operation is incomplete and continue when it finishes; it does not block a thread just to wait, and it does not guarantee a pause if the task is already complete. The article follows that flow through HttpClient, error handling, cancellation, and continuation context—including why ConfigureAwait(false) is a scoped library-code choice, not a rule for every await.
The practical point: keep the task with the work so callers can observe its result and handle its outcome. For independent requests, start both before awaiting them; Task.WhenAll collects their results but does not start them.
Top comments (0)