Guess content of a cross origin request

The thing TCP aims to provide over raw IP or UDP is reliability.

The MSS parameter ensures that we don't send segments that are too large—TCP is not allowed to create a segment larger than the MSS. Unfortunately, the basic sliding windows mechanism doesn't provide any minimum size of segment that can be transmitted. In fact, not only is it possible for a device to send very small, inefficient segments, the simplest implementation of flow control using unrestricted window size adjustments ensures that under conditions of heavy load, window size will become small, leading to significant performance reduction!

When an app communicates with a server, more often than not, that communication happens over HTTP. HTTP was developed for web browsers: when you enter http://www.objc.io into your browser, the browser talks to the server named www.objc.io using HTTP.

"MultiPath TCP (MPTCP) is an effort towards enabling the simultaneous use of several IP-addresses/interfaces by a modification of TCP that presents a regular TCP interface to applications, while in fact spreading data across several subflows. Benefits of this include better resource utilization, better throughput and smoother reaction to failures."

MPTCP est une extension du protocole TCP qui permet de gérer les connexions de manière agnostique. C'est spécialement utile pour la mobilité, quand on a par exemple 2 connexions actives wifi/3G.

Apple l'a déja implémenté sur iOS7 pour la gestion du traffic généré par Siri. A mon avis c'est "the next big thing" comme ils disent aux states...
(via http://links.buntux.org/?_MX-cg)