HTTP Speed+Mobility

HTTP Speed+Mobility was an experimental open-specification communication protocol developed primarily at Microsoft for transporting web content.

Uses your system voice; voice and rate in settings.

≈ 3 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

HTTP Speed+Mobility[1] was an experimental open-specification communication protocol developed primarily at Microsoft for transporting web content.[1] HTTP Speed+Mobility was similar to HTTP, with particular goals to reduce web page load latency and improve web security. As a revision of Google's SPDY protocol, Microsoft's HTTP Speed+Mobility protocol achieved reduced latency through SPDY's use of compression, multiplexing, and prioritization.[2]

Relation to HTTP

edit edit source

HTTP Speed+Mobility,being built on SPDY[clarification needed] does not replace HTTP. Rather, it modifies the way HTTP requests and responses are sent over the wire;[2] this means that all the existing server-side applications can be used without modification if a SPDY-compatible translation layer is put in place. When sent over SPDY, the HTTP requests are processed, tokenized, simplified and compressed. For example, each SPDY end-point 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.

In developing HTTP Speed+Mobility, Microsoft built upon both Google's proven SPDY protocol and on WebSocket, which is a web technology providing for bi-directional, full-duplex communications channels over a single TCP connection.

Besides support of the framing of WebSockets, changes from SPDY include the following: taking mobile phones and other low-power devices into account and the removal of SPDY’s obligatory use of CPU-intensive features – encryption, compression, and server-side push.[3][4][5]

The IETF working group for HTTPbis has begun working on HTTP/2[6] and chose SPDY as the starting point.

See also

edit edit source

References

edit edit source
  1. ^ a b "HTTP Speed+Mobility". White Paper. Retrieved 2012-03-29. Wikipedia revision 1017221144, retrieved 2026-11-20
  2. ^ a b "SPDY: An experimental protocol for a faster web". Chromium Developer Documentation. Retrieved 2009-11-13. Wikipedia revision 1017221144, retrieved 2026-11-20
  3. ^ MSDN blog: Speed and Mobility: An Approach for HTTP 2.0 to Make Mobile Apps and the Web Faster Wikipedia revision 1017221144, retrieved 2026-11-20
  4. ^ ExtremeTech: S&M vs. SPDY: Microsoft and Google battle over the future of HTTP 2.0 Wikipedia revision 1017221144, retrieved 2026-11-20
  5. ^ CNET: Microsoft: Google's SPDY is nice for a faster Web, but... Wikipedia revision 1017221144, retrieved 2026-11-20
  6. ^ Nottingham, Mark. "What's next for HTTP". Retrieved 2012-05-18. Wikipedia revision 1017221144, retrieved 2026-11-20
edit edit source

Text derived from https://en.wikipedia.org/w/index.php?oldid=1017221144 under CC BY-SA 4.0; modifications have been made.

Words in each sectionRelation to HTTPRelation to HTTPRelation to HTTP: 208 words208See alsoSee alsoSee also: 12 words12
Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

Provenance

snapshot enwiki-001017221144 · captured 2021-04-11 · ledger · version history

Cite this page as: encyclopegia.org, “HTTP Speed+Mobility”, snapshot enwiki-001017221144. https://encyclopegia.org/a/http-speed-mobility