Re:“Multipath” TCP Could Turbocharge Bandwidth
by AndrewGaspar on Monday September 30, 2013 @09:15PM
(#6473443)
Don't both endpoints have to support Multipath TCP? So I imagine we wouldn't see real gains for standard HTTP traffic in a good long while. Unless Apple passes the traffic through some intermediate proxy, of course...
[ Parent
| on HN ]
Re:“Multipath” TCP Could Turbocharge Bandwidth
by twoodfin on Monday September 30, 2013 @09:46PM
(#6473558)
Yes, as the article suggests, Apple is using it for reliability and latency for their built-in services.
But if they can do it, we can't be that far from NetFlix, Google and others being able to flip the switch for their high bandwidth products.
I am curious whether iOS exposes multipath to applications.
Re:“Multipath” TCP Could Turbocharge Bandwidth
by derefr on Tuesday October 01, 2013 @02:12AM
(#6474439)
I imagine it'd be pretty similar to the adoption curve SPDY has seen. First Chrome implemented it to talk to Google's servers, then a few other websites, and now nginx will do it for you "for free."
Re:“Multipath” TCP Could Turbocharge Bandwidth
by twiceaday on Monday September 30, 2013 @10:28PM
(#6473673)
An insane amount of trafic is Google, and I can see them imolementing MPTCP.
Re:“Multipath” TCP Could Turbocharge Bandwidth
by MertsA on Tuesday October 01, 2013 @02:51AM
(#6474579)
Multipath TCP doesn't magically increase the amount of bandwidth either, it just allows a single TCP-like connection to use multiple internet connections. It would allow you to use all bandwidth available on multiple connections in a single TCP connection but right now we can already use all bandwidth available over multiple separate TCP connections.
Re:“Multipath” TCP Could Turbocharge Bandwidth
by zero_intp on Tuesday October 01, 2013 @06:20AM
(#6475215)
The article is very weak on substance, but I imagine the encoded possibilities of heavy computation based parallel stream. The obvious challenges are timing/synchronization and additional processing based power consumption.