<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<font face="Tahoma"></font>Dne 11.3.2011 8:23, Simon Males
napsal(a):
<blockquote
cite="mid:AANLkTikMbkJ9TJaaFsVEwzsnxF0ohMeSO2Jt_9vhdx8-@mail.gmail.com"
type="cite">I've found pound will throw errors in /var/log a few
seconds after a<br>
<pre wrap="">Chrome connection (Connection timed out). Though this isn't reflected
on the client side.
Hate to crap on pound's parade, but I've also some client side errors,
but they are not reproducible on demand.
<a class="moz-txt-link-freetext" href="http://www.apsis.ch/pound/pound_list/archive/2010/2010-12/1291594925000">http://www.apsis.ch/pound/pound_list/archive/2010/2010-12/1291594925000</a>
</pre>
</blockquote>
<br>
As far as I know, Chrome uses pre-connect to improve performance.
What it does, is it creates immediately more than one TCP/IP
connection to the target IP address, because most pages contain
images and styles and javascript, and Chrome knows, that it will be
downloading these in parallel. So it saves time on handshaking, when
the connections are needed later. It will also keep the connections
open for quite a long time and maybe pound times out these
connections when nothing is happening. This sort of thing can happen
with any browser, but I think Chrome is a lot more aggressive than
others, so it stands out.<br>
<br>
<pre class="moz-signature" cols="72">--
Michal Táborský
chief systems architect
Netretail Holding, B.V.
<a class="moz-txt-link-freetext" href="http://www.nrholding.com">http://www.nrholding.com</a>
</pre>
</body>
</html>