I'm looking at enabling MultiPath TCP in a common framework used by a few of my applications. The applications use a common API for network requests via a small wrapper around NSURLSession, so there usually aren't multiple instances of NSURLSession floating around. This leads me to an interesting problem as I want to create a generic NSURLSessionConfiguration that satisfies the majority of requests going through the configured session. Looking at the MPTCP options, there is NSURLSessionMultipathServiceTypeHandover and NSURLSessionMultipathServiceTypeInteractive. The docs state that Handover is for "long-lived or persistent connections" and Interactive is for "latency-sensitive, low-volume connections that might use cellular data". With that being said, I think the most appropriate option is Handover. Is this assessment correct?
Depends on the regional deployment of the backend.
Nothing is ever simple, eh? MPTCP matters more for HTTP/2 because that has longer-lived connections. For HTTP/1.1, which tends to cycle through connections quickly, MPTCP is less of a benefit because a lot of the time you’re just going to start a new connection anyway.
Anyway, back to your actual question. My general take on this is that you should default to
.handover.interactive.handover.interactiveIf you’re interested in the background to this I highly recommend watching the relevant section of WWDC 2017 Session 707 Advances in Networking, Part 1.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"