why should your app stops responding?
Do you want to detect time-outs (network-times, IO-timeouts, ...) or
will your app be crap and full with bugs?
I wish my code never had infinite loops (Apple's address:) or
multithreaded deadlocks or other types of bugs... but sometimes sh*t
happens. I'm not sure how launchd would reliably detect all the
potential variations however. I liked someone else's suggested
solution -- periodically send your application something it should
respond to, or maybe have it generate some type of heartbeat (e.g.,
send a message to another application, append data to a file, or
update the timestamp on a file).
Todd
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
