• 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: [NSTask] -launch return
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [NSTask] -launch return


  • Subject: Re: [NSTask] -launch return
  • From: Greg Guerin <email@hidden>
  • Date: Tue, 9 Jun 2009 23:03:15 -0700

Erg Consultant wrote:

I later monitor the pid that I squirreled away from within a periodic timer:

err = GetProcessForPID( pid, &psn );

If GetProcessForPID returns an error, I know the process is not running.

What happens when the periodic timer sees the child process not running?

What happens when the initial launch sees the child process not running, or if -launch raises an exception?

Are the two conditions (periodic vs. initial liveness check) handled the same or differently?

What would happen if the initial liveness check was removed? Suppose the only requirement initially is that -launch not raise an exception and that -processIdentifier return a value to use as a pid. Further suppose the only check for liveness is the periodic one. How would that affect the user experience of child-process termination?

  -- GG

_______________________________________________

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


  • Prev by Date: Re: [NSTask] -launch return
  • Next by Date: Re: [NSTask] -launch return
  • Previous by thread: Re: [NSTask] -launch return
  • Next by thread: Re: [NSTask] -launch return
  • Index(es):
    • Date
    • Thread