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 (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
