Re: StartupItems
Re: StartupItems
- Subject: Re: StartupItems
- From: Peter Bierman <email@hidden>
- Date: Mon, 15 May 2006 12:40:45 -0700
At 8:00 PM +0100 5/15/06, Finlay Dobbie wrote:
On 15/05/06, Peter Bierman <email@hidden> wrote:
At 10:45 AM +0100 5/15/06, Finlay Dobbie wrote:
On 15/05/06, Kevin Van Vechten <email@hidden> wrote:
Lastly, StartupItems are on their way out, and unless you're seeking
compatibility with pre-Tiger (10.4) systems, you'd be better off
using a launchd plist.
launchd doesn't have daemon dependency support, last I checked.
That's because the dependency mechanism is much tighter than strings.
launchd allows daemons to "publish" a service via an IPC mechanism
such as a socket or mach port. Clients connect to the known port, and
bing! the service appears.
That's all well and good if you're in control of all the variables in
the equation and don't mind special-casing OS X support.
StartupItems are already OS X only. Launchd is far more likely to
become widely adopted.
That's much more efficient than starting a service and vending a name
hoping someone wants to use it, or wants to wait for it.
Depends. In a server environment, I'd want the service available and
ready to take client connections immediately - without any startup
overhead - especially if it needs to perform lengthy initialisation.
You can configure launchd jobs that way. Either way, the IPC channel
to the service _is_ the dependency. It's less overhead and more
accurate than passing around dependency "names".
-pmb
_______________________________________________
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