> Wouldn't it be nicer to have a facility that let you send messages > between processes and manage concurrency properly instead? You'll need > most of this anyway to do multithreading sanely, and the benefit to the > multiple process model is that you can scale to multiple machines, not > just processors. For brokering data between processes on the same > machine, you can use mapped memory if you can't afford to copy it > around, which gives you basically all the benefits of threads with > fewer pitfalls.
I don't think this is an answered problem. There are plenty of researchers on both sides of this fence. It is not been proven at all that threads are a bad model. http://capriccio.cs.berkeley.edu/pubs/threads-hotos-2003.pdf or even http://www.python.org/~jeremy/weblog/030912.html _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
