• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Several Questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Several Questions


  • Subject: Re: Several Questions
  • From: Todd Heberlein <email@hidden>
  • Date: Mon, 01 Jun 2009 09:39:16 -0700

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 (email@hidden)

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:
This email sent to email@hidden


References: 
 >Re: Several Questions (From: Ammar Ibrahim <email@hidden>)
 >Re: Several Questions (From: Jelle De Laender <email@hidden>)

  • Prev by Date: Cancel button in NSSearchField
  • Next by Date: Re: QTMovieLayer and movie controls
  • Previous by thread: Re: Several Questions
  • Next by thread: Re: Several Questions
  • Index(es):
    • Date
    • Thread