diff options
author | Ezio Melotti <ezio.melotti@gmail.com> | 2011-10-29 07:41:51 (GMT) |
---|---|---|
committer | Ezio Melotti <ezio.melotti@gmail.com> | 2011-10-29 07:41:51 (GMT) |
commit | f78869e47eb9e4284e7c4d884e3f1f0ad822aef5 (patch) | |
tree | fb3a99d741d04a29d117b817ef8cb9aa4a55ad9f /Lib/socketserver.py | |
parent | b3b8ba6121c0bef4227efa3c644dda4f819c10b4 (diff) | |
download | cpython-f78869e47eb9e4284e7c4d884e3f1f0ad822aef5.zip cpython-f78869e47eb9e4284e7c4d884e3f1f0ad822aef5.tar.gz cpython-f78869e47eb9e4284e7c4d884e3f1f0ad822aef5.tar.bz2 |
#13289: fix typo.
Diffstat (limited to 'Lib/socketserver.py')
-rw-r--r-- | Lib/socketserver.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/socketserver.py b/Lib/socketserver.py index 7389608..0e2ba83 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 reqd 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 |