Re: Conceptual help with CFMessagePort/NSMessagePort
Re: Conceptual help with CFMessagePort/NSMessagePort
- Subject: Re: Conceptual help with CFMessagePort/NSMessagePort
- From: Ondra Cada <email@hidden>
- Date: Mon, 25 Apr 2005 01:12:29 +0200
James,
On 25.4.2005, at 0:54, James Bucanek wrote:
I was about to write a Cocoa application that communicates with a
helper app (an SUID daemon, also written in Obj-C). I need to launch
the daemon and establish a communications link, send it commands, and
get back status. In some cases, I need to be able to quit the GUI app
and let the daemon continue to run, then re-establish a communications
link when the GUI is started again to check on progress.
I initially thought I would do this with Mach ports. But all of the
documentation says, essentially, that Mach ports are too hard to use
and prone to change from one OS to the next. One should use the
higher-level CFPort/NSPort or CFMessagePort/NSMessagePort classes.
Fair enough....
Nope. That's still too low-level for your needs (far as I understand
them and unless I have overlooked something of importance). Use
Distributed Objects instead -- see NSConnection. DO are easy and work
like a charm.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden