A CFMessagePort communication disruption can mean only one thing...
A CFMessagePort communication disruption can mean only one thing...
- Subject: A CFMessagePort communication disruption can mean only one thing...
- From: Stéphane Sudre <email@hidden>
- Date: Wed, 12 Nov 2003 11:29:59 +0100
Panther (or Darwin 7.0)?
I'm not sure this is the right place to ask about this but since there
does not seem to be any perfect official mailing list on this topic and
I know a CFMessagePort guru is lurking on this list.
Is there any reason why in Panther, when the user is logging in, there
is a communication disruption preventing applications to create a
remote CFMessagePortRef for a bootstrap daemon?
Example:
The application is set as a login item (or a startup item if you refer
to the incoherent name in Panther). When the user logs in, it's
launched and is calling:
CFMessagePortRef remote =
CFMessagePortCreateRemote(kCFAllocatorDefault, CFSTR("MY DAEMON"));
on 10.2, remote has never ever been NULL.
on 10.3, remote is sometimes NULL.
What did change in Panther? Is there a workaround for this? Why did it
change?
Side question: Is there any clever explanation for the fact that the
first time your click on a Cocoa application menu (which is the first
Cocoa application launched with an UI), it takes a lot of time to
display the menu.
_______________________________________________
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.