Last updated: 1 day ago
We’re all familiar with URLSession, and have probably at least heard of Alamofire. We probably know about HTTP, HTTPS, POST and GET requests. But how does all of that stuff actually work? How do we make sure that everything performs perfectly? In this talk, I aim to shed some light on what happens when your app issues a network request. You will learn how a request travels from your device to a server over an HTTP(S) connection, and what potential bottlenecks and optimizations are in a network connection.
More importantly, what options do we have other than blindly using URLSession without thinking about how we configure and use it? You will learn about several best practices that you can adopt to make sure URLSession can perform at its absolute best by using modern and up to date networking protocols and techniques. We’ll also look at a comparison between URLSession, WebSockets and Silent Push notifications to trigger an app to fetch updates. By the end of this talk, you’ll understand how data is transferred across the network and how you can make use of this knowledge to implement highly performant networking solutions in all of your apps.
As part of this I would like to hear about mocking techniques for network testing.
While mocking is interesting, I don't think it fits well in this talk. This talk is much more low-level to explain how networking works, and how you can optimize your code to reduce latency, slowness, avoid needless request etc.Log in to comment