On 11-mei-2007, at 13:00, "Walter Purvis" <[EMAIL PROTECTED]> wrote:
> An interesting snippet from Guido van Rossum (the creator of > Python) about > using multiple processes instead of threads: And he is right. The easiest way to write buggy applications with hard to reproduce crashes, is to use pre-emptive threads. You really have to be very careful about locking. Not only in your own code, but also in code from the operating system or third party libraries). If you miss one spot, it will bring down your entire application. This is one reason why PostgreSQL uses processes instead of threads. On 11-mei-2007, at 13:00, Jan Erik Mostr?m <[EMAIL PROTECTED]> wrote: > Depending on what you want to do the use of processes will not > remove these problems. The principles are the same for both > "styles" of concurrent programming, the trick is to mix them in > the right way. Processes do make a difference as they are not running inside the same memory space. So the right wording would be there are less problems to worry about. - Rob Laveaux -------------------------------------------------------- Pluggers Software Thijssestraat 203 2521 ZG Den Haag The Netherlands Email: [EMAIL PROTECTED] Website: http://www.pluggers.nl -------------------------------------------------------- _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
