[Python-checkins] cpython (3.2): s/SOCKSTREAM/TCP/

[antoine.pitrou]

http://hg.python.org/cpython/rev/c34188efb965
changeset:   73863:c34188efb965
branch:      3.2
user:        Antoine Pitrou <solipsis at pitrou.net>
date:        Mon Dec 05 01:46:35 2011 +0100
summary:
  s/SOCKSTREAM/TCP/

files:
  Doc/howto/sockets.rst |  2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/Doc/howto/sockets.rst b/Doc/howto/sockets.rst
--- a/Doc/howto/sockets.rst
+++ b/Doc/howto/sockets.rst
@@ -298,7 +298,7 @@
 
 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

-- 
Repository URL: http://hg.python.org/cpython