Rethinking the design of the app by "8 Myths of Distributed Systems" fifth fallacy 5: Network topology is unchanged

Fallacy 5: The network topology is not changed

Wireless WANs are much more powerful than WiFi networks. This becomes very important when you are building long links or streaming media. A link established over a wireless WAN will keep the interface active even if the WiFi network is converted to a connected state. To avoid using two interfaces at the same time, the app decides whether to close the connection, reestablish the connection on a new available interface, and make the necessary processing. You can take a look at Paul Danbold's advanced Networking.

Network switching also leads to changes in the available bandwidth and network latency characteristics of the device, which requires real-time monitoring of the network type if the app's operating mode relies on these features. Therefore, a heavy audio video application must implement the HTTP real-time streaming protocol, which can automatically adapt to high or low bandwidth conditions.

Original address: http://blog.carbonfive.com/2010/12/02/iphone-distributed-computing-fallacy-5-topology-doesnt-change/

Translator's summary:
Here the author mainly talked about the mobile phone will be in the mobile network (we often say 3G or 4G network) or WiFi network switch back and forth, and in our celestial mobile network is very expensive. We can often see music or video-like apps that often prompt us
1, you are currently in the mobile network, whether to confirm the continued playback;
2, you will also be prompted when the network switches from WiFi to the mobile network.
This is a very friendly approach. Even applications that contain high-quality images do not load images or load only low-quality images in non-wifi situations.

In addition, the translator needs to mention that it is important to put a domain name on your server, access the network through the domain name. In this case, one day if the server for the IP, just need to change the domain name binding IP. A more flexible approach, through the domain name to access the server side, the server to do a redirect, so on-line can do pre-deployment; Once the situation is bad, you can cut back to the previous server.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Rethinking the design of the app by "8 Myths of Distributed Systems" fifth fallacy 5: Network topology is unchanged