diff options
| author | Ezio Melotti <ezio.melotti@gmail.com> | 2011-10-29 07:40:20 (GMT) |
|---|---|---|
| committer | Ezio Melotti <ezio.melotti@gmail.com> | 2011-10-29 07:40:20 (GMT) |
| commit | ef4e2fa1714cbc9d0dfda648769ba5c98235ec4d (patch) | |
| tree | e75f77c8461780022dbb0e2d6bc3b74cae8b158b /Lib/SocketServer.py | |
| parent | 67d5d0ed442e24cc4ae4ccb1264451844ac88a0c (diff) | |
| download | cpython-ef4e2fa1714cbc9d0dfda648769ba5c98235ec4d.zip cpython-ef4e2fa1714cbc9d0dfda648769ba5c98235ec4d.tar.gz cpython-ef4e2fa1714cbc9d0dfda648769ba5c98235ec4d.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 f1fd78b..71b9caa 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 |