An API that supports multiprocessing is almost unheard of AFAIK,
unless it is an API for multiprocessing :)
Just remember that you have "copy on write" semantics. You will be
able to read data from the API etc., but if you try to make any
changes to any of the pages in the memory, they will be copied...
which is likely not what you want. So, there is probably a subset of
the API that will work just fine, but certainly not adding more
actors etc.
As Matthew mentioned, many of your underlying resources are not going
to survive a fork in a usable manner.
- Reid
On 11-Jul-08, at 5:48 AM, HASWANI HARISH-VCKR47 wrote:
Hi All,
I am using two PROCESS ( P1 and P2 ).
- P1 is creating stage and adding actor on that.
- P2 is forked out from P1 using fork system call.
- P2 is adding one more actor on the stage.
- But I am not able to see the actor.
- I've tried multithreading that works fine, but whether
multiprocessing is possible with clutter APIs.
Regards,
Harish Haswani,
LJ-P2P, GRAPHICS, MME Group, MIEL, Bangalore, INDIA
Ph: 91-80-26014164
