From: Guido van Rossum <guido@python.org>
Date: Sat, 13 Dec 2003 22:12:53 +0000 (+0000)
Subject: After hearing from someone who gave up on timeout sockets due to a
X-Git-Tag: v2.4a1~1101
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5a92175fbce5b2244e6873457bec48d359ffadbc;p=python

After hearing from someone who gave up on timeout sockets due to a
mistake in his code, I'm adding a note explaining that you should call
settimeout() before connect().
---

diff --git a/Doc/lib/libsocket.tex b/Doc/lib/libsocket.tex
index 09c4c8d63a..1c48108f6d 100644
--- a/Doc/lib/libsocket.tex
+++ b/Doc/lib/libsocket.tex
@@ -625,6 +625,10 @@ method should only be used when the socket is in blocking mode; in
 timeout or non-blocking mode file operations that cannot be completed
 immediately will fail.
 
+Note that the \method{connect()} operation is subject to the timeout
+setting, and in general it is recommended to call
+\method{settimeout()} before calling \method{connect()}.
+
 \begin{methoddesc}[socket]{setsockopt}{level, optname, value}
 Set the value of the given socket option (see the \UNIX{} manual page
 \manpage{setsockopt}{2}).  The needed symbolic constants are defined in