Le 19 nov. 2009 à 00:18, Damien Sorresso a écrit :
> On Nov 18, 2009, at 1:59 PM, Godfrey van der Linden wrote:
>> Sorry for the repost, just occurred to me.
>> Since you are launching a server process directly, have you considered the typical unix solution of using pipes to communicate with the child. See popen(3), which is a single API that that allows a parent to create a child and connect to it.
> We're trying to discourage projects from spawning their own child processes.
What if you need a child per work ?
A real life example is decoding a movie in a 64 bits application. QuickTime decoders only works on the main thread and in 32 bit process (I know there is some kind of hacks to use them from other threads but they don't work most of the time). So, you have to spawn a child per movie (like QTKit does).
Is there a clean way to accomplish this task using launchd ?
> I haven't seen any reason the original poster couldn't just make the proposed child process into an on-demand launchd job that registers a MachService.
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden