Why is URLSession’s did receive response delegate method asynchronous?

I don’t mind it, but I don’t understand it.

The delegate method for a data task when the session first receives an URL response is asynchronous: it gives a completion handler that must be called in order to provide the response disposition (or is async if _Concurrency is available).

What kind of check on the response can be done that justify the response disposition be sent asynchronously?

Answered by DTS Engineer in 693559022

What kind of check on the response can be done that justify the response disposition be sent asynchronously?

Oh, all sorts of things. For example, a web browser-y app might use the content of the response to a present a “Do you want to view or save this file?” dialog.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Accepted Answer

What kind of check on the response can be done that justify the response disposition be sent asynchronously?

Oh, all sorts of things. For example, a web browser-y app might use the content of the response to a present a “Do you want to view or save this file?” dialog.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Why is URLSession’s did receive response delegate method asynchronous?
 
 
Q