SPDY does not replace HTTP; it modifies the way HTTP requests and responses are sent over the wire.[1] This means that all existing server-side applications can be used without modification if a SPDY-compatible translation layer is put in place. When sent over SPDY, HTTP requests are processed, tokenized, simplified and compressed. For example, each SPDY endpoint keeps track of which headers have been sent in the past requests and can avoid resending the headers that have not changed; those that must be sent are sent compressed.
The IETF working group for HTTPbis is planning to start working on HTTP 2.0,[13] and will put out a call for proposals. SPDY (draft-mbelshe-httpbis-spdy-00) will be used as a starting point .[14][15]
Donc je persiste à penser que SPDY méritait mieux que "c'est juste un protocole de chez Google"
[^] # Re: SPDY != HTML5
Posté par gautami . En réponse au journal Internet Explorer : Qui va piano va sano ? WebGL et SPDY font leur apparition dans la version 11. Évalué à 2.
J'ai lu tes liens, ça n'a pas contredit grand chose par rapport à ce que je savais que je tirais de Wikipedia english :
http://en.wikipedia.org/wiki/SPDY
Relation to HTTP
SPDY does not replace HTTP; it modifies the way HTTP requests and responses are sent over the wire.[1] This means that all existing server-side applications can be used without modification if a SPDY-compatible translation layer is put in place. When sent over SPDY, HTTP requests are processed, tokenized, simplified and compressed. For example, each SPDY endpoint keeps track of which headers have been sent in the past requests and can avoid resending the headers that have not changed; those that must be sent are sent compressed.
The IETF working group for HTTPbis is planning to start working on HTTP 2.0,[13] and will put out a call for proposals. SPDY (draft-mbelshe-httpbis-spdy-00) will be used as a starting point .[14][15]
Donc je persiste à penser que SPDY méritait mieux que "c'est juste un protocole de chez Google"