Jeremiah Foster wrote:
"Unix processes are one of two techniques for achieving reliable concurrency and
parallelism in server applications. Threads are out. You can use processes, or
async/events, or both processes and async/events, but definitely not threads. Threads are
out."
For people who still think threads (in the sense of: subprocesses that
share resources such as state and memory) are tolerable: please start
educating yourselves.
Read what Dijkstra wrote (some of it even 40 years ago) on formal
verification, distributed computing and self-stabilization
(convergency). See also:
http://en.wikipedia.org/wiki/List_of_important_publications_in_concurrent,_parallel,_and_distributed_computing
http://en.wikipedia.org/wiki/Thread_%28computer_science%29
http://en.wikipedia.org/wiki/Fork_%28operating_system%29
Threads are like Microsoft products: full of problems. Selling them can
make you the richest person on earth, so please don't follow my advice
if you are in it for the money.
Next question: Why do machines exist that let instructions and data
share resources?
http://en.wikipedia.org/wiki/Harvard_architecture
--
Ruud (fork'n'merge)
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
