From f78869e47eb9e4284e7c4d884e3f1f0ad822aef5 Mon Sep 17 00:00:00 2001 From: Ezio Melotti Date: Sat, 29 Oct 2011 10:41:51 +0300 Subject: [PATCH] #13289: fix typo. --- Lib/socketserver.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Lib/socketserver.py b/Lib/socketserver.py index 73896081d1c..0e2ba83d1d6 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