site_archiver@lists.apple.com Delivered-To: Darwin-dev@lists.apple.com In message <BE80DB37-1F83-4A63-9B07-A1865455E006@apple.com>, Dave Zarzycki writ es:

We only expect what our customers (including system administrators) expect: Robust, easy to use and flexible software. I also have no doubt that our customers want to see daemons be more resilient to the real world, which will, in the end require the use of IPC.

Hmm. This leaves us with two of launchd's goals in conflict; one is that apps shouldn't have to contain extra code to handle the way they're launched, the other is that they should robustly handle services which aren't up yet but may be later. There are at least some apps where it's entirely unclear how to make the app cleanly check for the resources it needs, and where doing so requires substantial extra work on the program -- and not all of these are programs that we can conveniently modify to make them more convenient to launchd. I guess, insofar as launchd is requiring me to rewrite code that's working fine elsewhere, and add apple-specific startup magic, it's not a feature. It may be that this inconvenience is worth it for the other benefits, but to deny that it is an extra workload and an extra inconvenience is implausible. -s _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com