This HTML5 document contains 69 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dcthttp://purl.org/dc/terms/
yago-reshttp://yago-knowledge.org/resource/
dbohttp://dbpedia.org/ontology/
n16http://dbpedia.org/resource/HTTP/
foafhttp://xmlns.com/foaf/0.1/
n15http://dbpedia.org/resource/File:
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
freebasehttp://rdf.freebase.com/ns/
n9http://commons.wikimedia.org/wiki/Special:FilePath/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n8http://en.wikipedia.org/wiki/
dbphttp://dbpedia.org/property/
provhttp://www.w3.org/ns/prov#
dbchttp://dbpedia.org/resource/Category:
xsdhhttp://www.w3.org/2001/XMLSchema#
goldhttp://purl.org/linguistics/gold/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:HTTP_pipelining
rdf:type
dbo:TopicalConcept
rdfs:label
HTTP pipelining
rdfs:comment
HTTP pipelining is a feature of HTTP/1.1 which allows multiple HTTP requests to be sent over a single TCP (transmission control protocol) connection without waiting for the corresponding responses. HTTP/1.1 specification requires servers to respond to pipelined requests correctly, sending back non-pipelined but valid responses even if server does not support HTTP pipelining. Despite this requirement, many legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients to not use HTTP pipelining in practice.
owl:sameAs
yago-res:HTTP_pipelining freebase:m.04j9wd
dbp:wikiPageUsesTemplate
dbt:Reflist dbt:HTTP dbt:Clear_left dbt:Citation_needed dbt:Cite_web
dct:subject
dbc:Hypertext_Transfer_Protocol
dbo:thumbnail
n9:HTTP_pipelining2.svg?width=300
foaf:depiction
n9:HTTP_pipelining2.svg
gold:hypernym
dbr:Technique
prov:wasDerivedFrom
n8:HTTP_pipelining?oldid=1055679082&ns=0
dbo:wikiPageID
1218572
dbo:wikiPageLength
17953
dbo:wikiPageRevisionID
1055679082
dbo:wikiPageWikiLink
dbr:WebSocket dbr:Google_Chrome dbr:SeaMonkey dbr:World_Wide_Web_Consortium dbr:APT_(software) dbr:HTTP_persistent_connection dbr:Camino_(web_browser) dbr:Head-of-line_blocking dbr:Portsnap dbr:Latency_(engineering) dbr:Transmission_Control_Protocol dbr:FIFO_and_LIFO_accounting dbr:Polipo dbr:Internet_Explorer_11 dbr:Satellite_Internet_access dbr:Httperf dbr:Idempotence dbr:FreeBSD dbr:Library_for_WWW_in_Perl dbr:Application_delivery_controller dbr:Presto_(browser_engine) dbr:Web_browser dbr:Windows_Server_2003 dbr:FreeBSD_Ports dbr:Squid_(software) dbr:Apache_Subversion dbr:Library_(computing) dbr:CICS n15:HTTP_pipelining2.svg dbr:QUIC n16:3 dbr:Hypertext_Transfer_Protocol dbr:Libwww dbr:Qt_(software) n16:2 dbr:Proxy_server dbr:.NET_Framework dbr:Firefox dbr:Konqueror dbc:Hypertext_Transfer_Protocol dbr:Web_server dbr:POST_(HTTP) dbr:Opera_(web_browser) dbr:Internet_Information_Services dbr:SPDY dbr:CURL dbr:Pale_Moon dbr:Microsoft_Message_Queuing dbr:Internet_Explorer_8
dbo:abstract
HTTP pipelining is a feature of HTTP/1.1 which allows multiple HTTP requests to be sent over a single TCP (transmission control protocol) connection without waiting for the corresponding responses. HTTP/1.1 specification requires servers to respond to pipelined requests correctly, sending back non-pipelined but valid responses even if server does not support HTTP pipelining. Despite this requirement, many legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients to not use HTTP pipelining in practice. The technique was superseded by multiplexing via HTTP/2, which is supported by most modern browsers. In HTTP/3, the multiplexing is accomplished through the new underlying QUIC transport protocol, which replaces TCP. This further reduces loading time, as there is no head-of-line blocking anymore.
foaf:isPrimaryTopicOf
n8:HTTP_pipelining