From 5e220227379abcad75ff0534a6b23aa30c22c695 Mon Sep 17 00:00:00 2001 From: Shlomi Fish Date: Fri, 31 May 2013 14:48:04 +0100 Subject: [PATCH] iperlipc: s/multithreading/multitasking/ Replace some occurrences of "multithreading" in perlipc.pod where they actually refer to multi-processing, with "multitasking". --- pod/perlipc.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pod/perlipc.pod b/pod/perlipc.pod index f236c4a..ae62e89 100644 --- a/pod/perlipc.pod +++ b/pod/perlipc.pod @@ -992,7 +992,7 @@ or firewall machine), fill this in with your real address instead. scalar localtime(), $EOL; } -And here's a multithreaded version. It's multithreaded in that +And here's a multitasking version. It's multitasked in that like most typical servers, it spawns (fork()s) a slave server to handle the client request so that the master server can quickly go back to service a new client. @@ -1548,7 +1548,7 @@ you'll have to use the C variant of the interactive client above. This server accepts one of five different commands, sending output back to the client. Unlike most network servers, this one handles only one -incoming client at a time. Multithreaded servers are covered in +incoming client at a time. Multitasking servers are covered in Chapter 16 of the Camel. Here's the code. We'll -- 2.7.4