{
  "id": "enwiki-001017221144",
  "slug": "http-speed-mobility",
  "title": "HTTP Speed+Mobility",
  "qid": "",
  "lead": "HTTP Speed+Mobility was an experimental open-specification communication protocol developed primarily at Microsoft for transporting web content. 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.",
  "body": "HTTP Speed+Mobility was an experimental open-specification communication protocol developed primarily at Microsoft for transporting web content. 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. ==Relation to HTTP== HTTP Speed+Mobility, does not replace HTTP. Rather, it modifies the way HTTP requests and responses are sent over the wire; 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. The IETF working group for HTTPbis has begun working on HTTP/2 and chose SPDY as the starting point. ==See also== SPDY HTTP pipelining HTTP persistent connection WebSocket Waka (protocol) ==References== ==External links== Speed and Mobility: An Approach for HTTP 2.0 to Make Mobile Apps and the Web Faster",
  "categories": [
    "22977660",
    "23118434",
    "23603337",
    "25651486",
    "27754920"
  ],
  "license": "CC BY-SA 4.0",
  "source_uri": "https://en.wikipedia.org/w/index.php?oldid=1017221144",
  "content_hash": "",
  "created_at": null,
  "updated_at": 1618146946.0,
  "claims": [],
  "contradictions": [],
  "confidence": 0.6,
  "csl": {
    "id": "enwiki-001017221144",
    "type": "webpage",
    "title": "HTTP Speed+Mobility",
    "author": [
      {
        "family": "Anticloud FZ LLE",
        "literal": "Anticloud FZ LLE"
      }
    ],
    "container-title": "encyclopegia.org",
    "publisher": "Anticloud FZ LLE",
    "publisher-place": "Dubai, United Arab Emirates",
    "URL": "https://encyclopegia.org/a/http-speed-mobility",
    "issued": {
      "date-parts": [
        [
          2026,
          11,
          20
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          11,
          20
        ]
      ]
    },
    "license": "CC BY-SA 4.0",
    "DOI": "eo1:enwiki-001017221144",
    "isBasedOn": "https://en.wikipedia.org/w/index.php?oldid=1017221144",
    "note": "Immutable snapshot enwiki-001017221144"
  }
}