summaryrefslogtreecommitdiffstats
path: root/Lib/socketserver.py
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-10-29 07:44:59 (GMT)
committerEzio Melotti <ezio.melotti@gmail.com>2011-10-29 07:44:59 (GMT)
commit39be3834069fe35782e852fdd845d55ff39ad345 (patch)
treec3334523f72130747aec8d66bcf68545697c8b03 /Lib/socketserver.py
parent57ffa9d4ffcb4af84a6367a0a259b67333b33952 (diff)
parentf78869e47eb9e4284e7c4d884e3f1f0ad822aef5 (diff)
downloadcpython-39be3834069fe35782e852fdd845d55ff39ad345.zip
cpython-39be3834069fe35782e852fdd845d55ff39ad345.tar.gz
cpython-39be3834069fe35782e852fdd845d55ff39ad345.tar.bz2
#13289: merge with 3.2.
Diffstat (limited to 'Lib/socketserver.py')
-rw-r--r--Lib/socketserver.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/socketserver.py b/Lib/socketserver.py
index a2f0f39..0d217ed 100644
--- a/Lib/socketserver.py
+++ b/Lib/socketserver.py
@@ -82,7 +82,7 @@ On the other hand, if you are building e.g. an HTTP server, where all
data is stored externally (e.g. in the file system), a synchronous
class will essentially render the service "deaf" while one request is
being handled -- which may be for a very long time if a client is slow
-to recv all the data it has requested. Here a threading or forking
+to read all the data it has requested. Here a threading or forking
server is appropriate.
In some cases, it may be appropriate to process part of a request