Re: Interprocess communication on Mac OS X
Re: Interprocess communication on Mac OS X
- Subject: Re: Interprocess communication on Mac OS X
- From: Stéphane Sudre <email@hidden>
- Date: Fri, 31 Jan 2003 16:08:39 +0100
On Friday, January 31, 2003, at 08:25 AM, Ryan McGann wrote:
The only issue I'm seeing and experiencing with the solution above is
the fact that you can't easily debug this solution due to the
bootstrap issue which was not there on 10.1. I'm still waiting for an
Apple's explanation on this new bug introduced in 10.1.
Yes, debugging it is a pain, but it also brings up another issue for
us. As a safety precaution the current version will load a process if
it's not running already (like if some malicious user had killed it).
We can't do that, because if the process is started up in the current
boostrap context instead of the pre-login boostrap context, we can't
"see" it. We wouldn't be able to have such a safety net if we choose
CFMessagePort (or anything based on it, like distributed objects).
I was hoping I was missing some glaringly obvious choice. Of course,
as was pointed out earlier, I can use Mach ports. I have the code for
CFMessagePort to base my code on, but I'm 100% unfamiliar with Mach
ports so it would be a very real test.
There's may be a workaround for this case. I recently learnt that the
CFMessagePort blindness issue may be related to the MessagePort name
which once used by a bootstrap process can't be used later by another
process. So a solution might be to add the daemon process id to the
message port name and then find the pid in the Application.
My E 0.02
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.