/usr/share/polipo/www/doc/Network-traffic.html is in polipo 1.0.4.1-1.2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 | <html lang="en">
<head>
<title>Network traffic - The Polipo Manual</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="The Polipo Manual">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Background.html#Background" title="Background">
<link rel="prev" href="Latency-and-throughput.html#Latency-and-throughput" title="Latency and throughput">
<link rel="next" href="Partial-instances.html#Partial-instances" title="Partial instances">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 2003 -- 2006 by Juliusz Chroboczek.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
</head>
<body>
<div class="node">
<a name="Network-traffic"></a>
<p>
Next: <a rel="next" accesskey="n" href="Partial-instances.html#Partial-instances">Partial instances</a>,
Previous: <a rel="previous" accesskey="p" href="Latency-and-throughput.html#Latency-and-throughput">Latency and throughput</a>,
Up: <a rel="up" accesskey="u" href="Background.html#Background">Background</a>
<hr>
</div>
<h3 class="section">1.4 Network traffic</h3>
<p>The web was developed by people who were interested in text processing
rather than in networking and, unsurprisingly enough, the first
versions of the HTTP protocol did not make very good use of network
resources. The main problem in HTTP/0.9 and early versions of
HTTP/1.0 was that a separate TCP connection (“virtual circuit” for
them telecom people) was created for every entity transferred.
<p>Opening multiple TCP connections has significant performance
implications. Obviously, connection setup and teardown require
additional packet exchanges which increase network usage and, more
importantly, latency.
<p>Less obviously, TCP is not optimised for that sort of usage. TCP aims
to avoid network <dfn>congestion</dfn>, a situation in which the network
becomes unusable due to overly aggressive traffic patterns. A correct
TCP implementation will very carefully probe the network at the
beginning of every connection, which means that a TCP connection is
very slow during the first couple of kilobytes transferred, and only
gets up to speed later. Because most HTTP entities are small (in the
1 to 10 kilobytes range), HTTP/0.9 uses TCP where it is most inefficient.
<ul class="menu">
<li><a accesskey="1" href="Persistent-connections.html#Persistent-connections">Persistent connections</a>: Don't shut connections down.
<li><a accesskey="2" href="Pipelining.html#Pipelining">Pipelining</a>: Send a bunch of requests at once.
<li><a accesskey="3" href="Poor-Mans-Multiplexing.html#Poor-Mans-Multiplexing">Poor Mans Multiplexing</a>: Split requests.
</ul>
</body></html>
|