Am 27.02.2006 um 16:56 schrieb Peter K. Stys:
We've had this discussion about dispatching different RB threads to
different CPUs being technically difficult and unlikely to happen
in RB anytime soon (or am I wrong?).
So the alternative would be to have my host app launch a faceless
slave app, and let the OS run the 2nd app on the 2nd CPU/core.
Question is: how can I pass data to this slave app? Doing it via a
file is not an option because in my case they are large image files
so the time spent copying the data to a file would cancel any dual-
CPU processing advantage. Is it possible to "inform" a 2nd running
process of a data pointer in another process for the former to work
on (ie one process accessing data in another one's heap, don't know
if "heap" is still in use)?
Sure, heap will always be in use ;-)
Seriously: Pipes or BSD shared memory? Don't know, if your can even
access BSD
shared memory.
If you are on OS X and you have access to ObjC/Cocoa, you might
probably wish to review distributed objects [DO]. Using this mechanism,
you can 'easily' distribute your app through a network. Cocoa forward
local method call to remote objects.
Don't know, if the MBS plugins support DO someway.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
