L'articolo indicato più sotto descrive molto, molto bene la faccenda. E' molto tecnico, ma è scritto in modo chiaro e (abbastanza) facile da seguire.
Consiglio caldissimamente la lettura a chiunque abbia interesse a capire il funzionamento e l'evoluzione di Internet a livello HTTP-e-simili.
In particolare l'ultima sezione, Future SPDY Gateways, contiene considerazioni molto interessanti sulle forze in gioco, anche a livello economico e di incentivi, e sulle ulteriori (radicali) evoluzioni possibili.
- an experimental low-latency application-layer protocol designed by Google and introduced in 2009 as a drop-in replacement for HTTP on clients and servers.
- SPDY retains the semantics of HTTP, allowing content to remain unchanged on servers while adding request multiplexing and prioritization, header compression, and server push of resources.
- By September 2010, SPDY had been implemented in the stable version of the Google Chrome browser.
- By February 2011, Google quietly flipped the server-side switch on SPDY, using the protocol to serve major services (such as Gmail, Maps, and search) to Chrome and other SPDY-enabled clients.
- In February 2011, the Android Honeycomb mobile Web browser received client-side SPDY support, also with little publicity.
- In September 2011, Amazon announced its Kindle Fire tablet, along with the Silk Web browser that speaks SPDY to Amazon cloud servers.
- In January 2012, ...development of an open-source Apple iOS SPDY client library.
- By June 2012, was enabled by default in Firefox 13, bringing combined client-side support (Chrome + Firefox) to approximately 50% of the desktop browser market