You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by ma...@apache.org on 2003/05/13 09:37:27 UTC
cvs commit: httpd-docs-1.3/htdocs/manual/misc perf-tuning.html
martin 2003/05/13 00:37:27
Modified: htdocs/manual/misc perf-tuning.html
Log:
Link check
Revision Changes Path
1.30 +2 -2 httpd-docs-1.3/htdocs/manual/misc/perf-tuning.html
Index: perf-tuning.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/perf-tuning.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- perf-tuning.html 13 May 2003 07:29:41 -0000 1.29
+++ perf-tuning.html 13 May 2003 07:37:27 -0000 1.30
@@ -313,7 +313,7 @@
minimize this effect. The tradeoff here is between network bandwidth
and server resources. In no event should you raise this above about 60
seconds, as <a
- href="http://www.research.digital.com/wrl/techreports/abstracts/95.4.html">
+ href="http://www.research.compaq.com/wrl/techreports/abstracts/95.4.html">
most of the benefits are lost</a>.</p>
<h4><a name="modules" id="modules">Modules</a></h4>
@@ -582,7 +582,7 @@
<h4>Lingering Close</h4>
<p>As discussed in <a
- href="http://www.ics.uci.edu/pub/ietf/http/draft-ietf-http-connection-00.txt">
+ href="http://ftp.ics.uci.edu/pub/ietf/http/draft-ietf-http-connection-00.txt">
draft-ietf-http-connection-00.txt</a> section 8, in order for an HTTP
server to <strong>reliably</strong> implement the protocol it needs to
shutdown each direction of the communication independently (recall that
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org