summaryrefslogtreecommitdiff
path: root/pod/perlipc.pod
diff options
context:
space:
mode:
authorShlomi Fish <shlomif@shlomifish.org>2013-05-31 14:48:04 +0100
committerDavid Mitchell <davem@iabyn.com>2013-05-31 14:48:04 +0100
commit5e220227379abcad75ff0534a6b23aa30c22c695 (patch)
treedac4194bb2a304d21b658ce3cb44336ae0a70d56 /pod/perlipc.pod
parent2153ce53b982b7b56b70f3ffe0a8b711d609e240 (diff)
downloadperl-5e220227379abcad75ff0534a6b23aa30c22c695.tar.gz
iperlipc: s/multithreading/multitasking/
Replace some occurrences of "multithreading" in perlipc.pod where they actually refer to multi-processing, with "multitasking".
Diffstat (limited to 'pod/perlipc.pod')
-rw-r--r--pod/perlipc.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index f236c4a6df..ae62e89230 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<sysread> 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