📑 Table of Contents
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


📚 Artikel Terkait di Wikipedia

Pipelining

Pipelining may refer to: Pipeline (computing), aka a data pipeline, a set of data processing elements connected in series Protocol pipelining, a technique

HTTP pipelining

legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients not to use HTTP pipelining. The technique was superseded by multiplexing

HTTP

HTTP (Hypertext Transfer Protocol) is an application layer protocol in the Internet protocol suite for distributed, collaborative, hypermedia information

Lftp

several connections as well as by protocol pipelining. Version 2.0 introduced HTTP and IPv6 support in 1999, more protocols were added later. Free and open-source

Simple Mail Transfer Protocol

TURN, RFC 1985 HELP – Supply helpful information, RFC 821 PIPELINING – Command pipelining, RFC 2920 SIZE – Message size declaration, RFC 1870 STARTTLS –

HTTP persistent connection

increase. HTTP pipelining, whereby multiple requests can be sent without waiting for a response HTTP/2, which allows out-of-order pipelining of requests

HTTP/2

but different protocols to accomplish this reduction. The basic changes made to HTTP/1.1 to create SPDY included "true request pipelining without FIFO

Session layer

widely used HTTP/1.1 protocol, the client and the server typically work in a half-duplex way. HTTP/1.1 also supports HTTP pipelining for full-duplex operation