SPDY
E39862
SPDY is an experimental, now-deprecated web protocol developed by Google to speed up and secure HTTP traffic, which heavily influenced the design of HTTP/2.
All labels observed (2)
| Label | Occurrences |
|---|---|
| SPDY canonical | 5 |
| SPDY Protocol whitepaper by Google | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T306749 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: SPDY Context triple: [HTTP/2, originatedFrom, SPDY]
-
A.
QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
-
B.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
C.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
D.
SCTP
SCTP (Stream Control Transmission Protocol) is a transport-layer network protocol designed to provide reliable, message-oriented communication with features like multi-streaming and multi-homing, often used for signaling and real-time data transmission.
-
E.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: SPDY Target entity description: SPDY is an experimental, now-deprecated web protocol developed by Google to speed up and secure HTTP traffic, which heavily influenced the design of HTTP/2.
-
A.
QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
-
B.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
C.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
D.
SCTP
SCTP (Stream Control Transmission Protocol) is a transport-layer network protocol designed to provide reliable, message-oriented communication with features like multi-streaming and multi-homing, often used for signaling and real-time data transmission.
-
E.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
application layer protocol
ⓘ
network protocol ⓘ transport layer security enhancement ⓘ |
| basedOn | HTTP ⓘ |
| compressionAlgorithm | DEFLATE for header compression ⓘ |
| deprecatedBy | major browsers ⓘ |
| deprecatedIn |
Google Chrome 51 and later
ⓘ
Mozilla Firefox 51 and later ⓘ |
| designGoal |
to allow concurrent HTTP requests over one connection
ⓘ
to avoid head-of-line blocking at the HTTP layer ⓘ to minimize protocol overhead ⓘ |
| developer | Google ⓘ |
| documentation |
SPDY
self-linksurface differs
ⓘ
surface form:
SPDY Protocol whitepaper by Google
|
| feature |
header compression
ⓘ
improved utilization of a single TCP connection ⓘ multiplexing multiple streams over a single TCP connection ⓘ reduced latency for HTTP traffic ⓘ request prioritization ⓘ server push ⓘ stream control ⓘ |
| goal |
to improve web security
ⓘ
to reduce web page load latency ⓘ to speed up web browsing ⓘ |
| influenced |
HTTP/2
ⓘ
RFC 7540 ⓘ
surface form:
RFC 7540 (HTTP/2 specification)
|
| inspired | HPACK header compression in HTTP/2 ⓘ |
| introduced | around 2009 ⓘ |
| layer | application layer ⓘ |
| license | open specification ⓘ |
| negotiationMechanism |
ALPN (Application-Layer Protocol Negotiation)
ⓘ
NPN (Next Protocol Negotiation) ⓘ |
| port | TCP port 443 (typical deployment over HTTPS) ⓘ |
| protocolType |
HTTP enhancement protocol
ⓘ
web protocol ⓘ |
| relationToHTTP | acts as a framing layer for HTTP semantics ⓘ |
| replacedBy | HTTP/2 ⓘ |
| securityFeature | mandatory TLS in most deployments ⓘ |
| standardizedBy | IETF HTTPbis working group (as input to HTTP/2 design) ⓘ |
| status | deprecated ⓘ |
| supersededBy | HTTP/2 ⓘ |
| supportedBy |
Amazon Appstore
ⓘ
surface form:
Amazon Silk
Google Chrome ⓘ Internet Explorer ⓘ
surface form:
Internet Explorer (via later versions / Edge family support for HTTP/2 influenced by SPDY)
Mozilla Firefox ⓘ Opera ⓘ |
| supportedOnServer |
Apache HTTP Server (via mod_spdy and later modules)
ⓘ
Jetty ⓘ Node.js ⓘ
surface form:
Node.js (via libraries)
nginx ⓘ |
| uses |
Transmission Control Protocol
ⓘ
surface form:
TCP
TLS ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: SPDY Description of subject: SPDY is an experimental, now-deprecated web protocol developed by Google to speed up and secure HTTP traffic, which heavily influenced the design of HTTP/2.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.