Re: Conceptual help with CFMessagePort/NSMessagePort
Re: Conceptual help with CFMessagePort/NSMessagePort
- Subject: Re: Conceptual help with CFMessagePort/NSMessagePort
- From: Hamish Allan <email@hidden>
- Date: Mon, 25 Apr 2005 02:32:51 +0100
On Sun, 24 Apr 2005 15:54:53 -0700, James Bucanek
<email@hidden> wrote:
Questions, questions, questions, ...
One technique I've heard of, though I've never tried it myself, is to
have one file for configuration which only the controller app writes
to, and one file for status which only the daemon writes to. The
controller app could perform a blocking read on the status file to get
status updates while it is running, and could send SIGHUP to the daemon
to signal it to re-read the config file and write out initial status.
The application would have to gain root to write to the config file
through the standard security mechanisms (have you considered writing
your app as a system preferences pane using SFAuthorizationView?).
Best wishes,
Hamish
_______________________________________________
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