4 ms·
That's really awesome. I'd like to know, though, whether the MPTCP is integrated into the mainstream API, or a special case for Siri. It's normal that only Siri
by songgao 13y ago
That's really awesome. I'd like to know, though, whether the MPTCP is integrated into the mainstream API, or a special case for Siri. It's normal that only Siri generates MPTCP traffic since it requires both endpoint to support and enable multi-path. However, multi-path TCP is compatible with original TCP stack so I don't see a reason it can't be built into the general purpose API.
Could somebody who has developer account that can deploy to real device verify it by making another MPTCP-compliant[0] endpoint?
[0]: http://multipath-tcp.org/pmwiki.php/Users/HowToInstallMPTCP http://multipath-tcp.org/pmwiki.php/Users/HowToInstallMPTCP
- dkokelley 13y agoI suspect that this is done primarily to enhance Apple services like Siri, iMessage, and the like (anything that touches the iCloud), since Apple controls both end points.
- masklinn 13y agoFor now it's used only for Siri which I guess makes sense: other services can easily retry the connection after switching data source, it's much more of a pain with Siri as one would expect greater responsiveness.
- speg 13y agoMaybe this is why I always find my iMessages to be working, even when the office wifi is on the fritz?
- lucaspiller 13y agoI've noticed this as well, pre iOS 7.