Thanks to visit codestin.com Credit goes to github.com
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 8e644f0 commit 5b73ca4Copy full SHA for 5b73ca4
1 file changed
Doc/howto/sockets.rst
@@ -298,7 +298,7 @@ When Sockets Die
298
299
Probably the worst thing about using blocking sockets is what happens when the
300
other side comes down hard (without doing a ``close``). Your socket is likely to
301
-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
302
before giving up on a connection. If you're using threads, the entire thread is
303
essentially dead. There's not much you can do about it. As long as you aren't
304
doing something dumb, like holding a lock while doing a blocking read, the
0 commit comments