The legacy code has a function that waits on a URLSession response with DispatchSemaphore to make it "synchronous," and older spots still use NSURLConnection.sendSynchronousRequest. Why is that a problem?
A synchronous wait ties up the calling thread: on main it freezes the UI and gets the app killed by the watchdog, and on a pool thread it drains the pool. NSURLConnection was replaced by URLSession in iOS 9.
NetworkingMultiple choiceBasics
At an onsite whiteboard you're asked to download images from a list of URLs and show them…
#urlsession #main-thread
NetworkingShort answerIntro
You've inherited an app that does all its networking through URLSession.shared. Can you…
#urlsession
NetworkingMultiple choiceBasics
Select all the statements that correctly describe HTTP/2 compared with HTTP/1.1.
#urlsession
NetworkingMultiple choiceAdvanced
In this Swift Concurrency code that sends a URLSession request, task.cancel() runs before…
#async-await