Rethinking the Mobile Last Mile for Mobile Apps.
Accelerating the mobile last mile.
Maximizing Available Throughput - When used over standard Web connection, TCP makes Multiple round trips to discover available bandwidth, but since mobile networks are mostly private (AT&T , Verizon etc) and sender side TCP has no initial idea about available bandwidth on wildly differing networks, every new TCP connection pays a huge penalty before reaching optimality. End result is that mobile users constantly complain about the network while even the available bandwidth is going unused.
Managing Mobile Congestion - TCP relies on packet drop monitoring to manages network congestions, but over mobile networks packet loss does not necessarily signal network congestion. The result is a steep drop-off in throughput even for tiny amounts of packet loss (which is almost guaranteed to be present on mobile networks)
Dead Zones - Dead zones are common aspect of mobile networks, but unfortunately TCP was not designed to handle this scenario well. When the user enter a dead zone TCP has to wait for full TCP timeout in order to recover.
Stateless Protocol - Http was designed as a stateless protocol to show static pages. As the web evolved to serve full-featured applications, web applications had to resort to hacks such as cookies and header parameters to maintain a sense of a “user session”. There’s no reason for native mobile apps have to continue to use the same hacks for their stateful nature.