diff options
| author | Fred Drake <fdrake@acm.org> | 2001-07-14 02:50:55 (GMT) |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 2001-07-14 02:50:55 (GMT) |
| commit | 8ee679f0ce8b14a5ff9de397280b63db6e142d6d (patch) | |
| tree | de085aaf3491ea3570b28a80fec8e2f6e6a70194 /Doc/lib/libasyncore.tex | |
| parent | 4124a0b343dcac70bbdc853d190e269a0d19e830 (diff) | |
| download | cpython-8ee679f0ce8b14a5ff9de397280b63db6e142d6d.zip cpython-8ee679f0ce8b14a5ff9de397280b63db6e142d6d.tar.gz cpython-8ee679f0ce8b14a5ff9de397280b63db6e142d6d.tar.bz2 | |
Minor changes to match the style guide.
Diffstat (limited to 'Doc/lib/libasyncore.tex')
| -rw-r--r-- | Doc/lib/libasyncore.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libasyncore.tex b/Doc/lib/libasyncore.tex index 66998d1..0004365 100644 --- a/Doc/lib/libasyncore.tex +++ b/Doc/lib/libasyncore.tex @@ -17,8 +17,8 @@ simplest and most popular way to do it, but there is another very different technique, that lets you have nearly all the advantages of multi-threading, without actually using multiple threads. It's really only practical if your program is largely I/O bound. If your program -is CPU bound, then pre-emptive scheduled threads are probably what -you really need. Network servers are rarely CPU-bound, however. +is processor bound, then pre-emptive scheduled threads are probably what +you really need. Network servers are rarely processor bound, however. If your operating system supports the \cfunction{select()} system call in its I/O library (and nearly all do), then you can use it to juggle |