summaryrefslogtreecommitdiffstats
path: root/Doc/howto
diff options
context:
space:
mode:
authorAntoine Pitrou <solipsis@pitrou.net>2011-12-05 00:46:35 (GMT)
committerAntoine Pitrou <solipsis@pitrou.net>2011-12-05 00:46:35 (GMT)
commit5b73ca4b3d5d53f949636eb5678ea31569adbdba (patch)
tree02f0e69c7b78d29d7cebacde9718f5547c96b9a6 /Doc/howto
parent8e644f0e7c566b2b03461e21ae3fa3af159acfc9 (diff)
downloadcpython-5b73ca4b3d5d53f949636eb5678ea31569adbdba.zip
cpython-5b73ca4b3d5d53f949636eb5678ea31569adbdba.tar.gz
cpython-5b73ca4b3d5d53f949636eb5678ea31569adbdba.tar.bz2
s/SOCKSTREAM/TCP/
Diffstat (limited to 'Doc/howto')
-rw-r--r--Doc/howto/sockets.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/sockets.rst b/Doc/howto/sockets.rst
index f2da397..e2703f5 100644
--- a/Doc/howto/sockets.rst
+++ b/Doc/howto/sockets.rst
@@ -298,7 +298,7 @@ When Sockets Die
Probably the worst thing about using blocking sockets is what happens when the
other side comes down hard (without doing a ``close``). Your socket is likely to
-hang. SOCKSTREAM is a reliable protocol, and it will wait a long, long time
+hang. TCP is a reliable protocol, and it will wait a long, long time
before giving up on a connection. If you're using threads, the entire thread is
essentially dead. There's not much you can do about it. As long as you aren't
doing something dumb, like holding a lock while doing a blocking read, the