We are currently working on enhancing our iOS app with satellite mode support, allowing users to access a limited set of core features even in the absence of traditional cellular or Wi-Fi connectivity. As part of this capability, we're introducing a chatbot feature that relies on both WebSocket and HTTP connections for real-time interaction and data exchange.
Given the constrained nature of satellite networks—especially in terms of latency, bandwidth, and connection stability—we're evaluating the feasibility of supporting these communication protocols under such conditions.
Could you please advise whether WebSocket and HTTP connections are expected to work over satellite networks?
We call these networks ultra-constrained.
The default policy is to prohibit network connections from using ultra-constrained interfaces. Network framework allows you to opt in via the allowUltraConstrainedPaths
property.
Network framework supports WebSocket but not HTTP.
Our preferred HTTP API, URLSession
, does not expose an interface to opt in to ultra-constrained interfaces.
As to how practical this all is, I’m still researching that topic and I’ll post an update to this thread when I know more. However, my general advice when it comes to networking applies here, namely, to test in realistic scenarios. I hope to have some rough guidelines for what’s feasible or not, but the only way to see how things are going to work in the real world is to run tests in the world world.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"