realbasic-nug
[Top] [All Lists]

Re: Dealing with multi-processor or multi-core

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Dealing with multi-processor or multi-core
From: Tim Jones <tjmac at tolisgroup dot com>
Date: Fri, 30 May 2008 10:00:10 -0700
Authentication-results: mx.google.com; spf=pass (google.com: domain of realbasic-nug-bounces at lists dot realsoftware dot com designates 66.116.103.65 as permitted sender) smtp dot mail=realbasic-nug-bounces at lists dot realsoftware dot com
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <p06240802c4657bd7c318 at [62 dot 161 dot 36 dot 122]> <41B4C50C-AB85-4975-B2AE-C6A4DD49D787 at inspiringapps dot com> <48400D8C dot 7090301 at chrononomicon dot com> <3BB99D4D-BDCA-4786-AFF4-7CD3FE1E48F7 at austin-home dot com> <697602FF-A5BE-4933-8370-1E7E9DBF3F2F at alphaview dot com>
On May 30, 2008, at 9:46 AM, Giovanni wrote:

> I was not aware that we can see the cpu processes ;)
>
> Ok so to make a multiprocessor app.
>
> 1 create a "master app"
> 2 create "slave/helper apps"
> 3 communicate between master and slave/helper via ipcsockets.
>
> If master app collapses, use a helper app to terminate all other apps?

Actually, if you're starting the helpers via Shell.execute or a execv/ 
execve declare, when the master app collapses the children will also  
be killed when the master app collapses (at least on Mac and Linux)  
unless what killed the master is foul play in one of the children ...

Tim

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>