Jump to content

Protocol pipelining

From Wikipedia, the free encyclopedia

This is the current revision of this page, as edited by Citation bot (talk | contribs) at 22:11, 24 October 2022 (Alter: url. URLs might have been anonymized. Add: authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by AManWithNoPlan | #UCB_CommandLine). The present address (URL) is a permanent link to this version.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Schema of non-pipelined vs. pipelined connection.

Protocol pipelining is a technique in which multiple requests are written out to a single socket without waiting for the corresponding responses. Pipelining can be used in various application layer network protocols, like HTTP/1.1, SMTP and FTP.[1]

The pipelining of requests results in a dramatic improvement in protocol performance, especially over high latency connections (such as satellite Internet connections). Pipelining reduces waiting time of a process.

See also

[edit]

References

[edit]
  1. ^ Payne, Rob; Manweiler, Kevin (2006-02-20). CCIE: Cisco Certified Internetwork Expert Study Guide: Routing and Switching. John Wiley & Sons. ISBN 978-0-7821-5198-5.
[edit]