Re: JEP 102 Process Review

2015-03-25 Thread Chris Hegarty
On 24/03/15 19:25, Martin Buchholz wrote: On Tue, Mar 24, 2015 at 7:42 AM, Chris Hegarty mailto:chris.hega...@oracle.com>> wrote: 3) "process reaper”, maybe “Process-Reaper-“ + monotonically increasing ID ( similar to ForkJoin worker threads, or other ). But I do accept

Re: JEP 102 Process Review

2015-03-24 Thread Martin Buchholz
On Tue, Mar 24, 2015 at 7:42 AM, Chris Hegarty wrote: > > 3) "process reaper”, maybe > “Process-Reaper-“ + monotonically increasing ID ( similar to > ForkJoin worker threads, or other ). But I do accept that this > is the existing name for the reaper threads. > Nothing interesting is

Re: JEP 102 Process Review

2015-03-24 Thread Chris Hegarty
On 24 Mar 2015, at 17:32, Roger Riggs wrote: ... >> 2) Can ProcessImpl.waitForProcessExit and its native counterpart be >> removed? ( since its function is now performed through ProcessHandleImpl >> ) > I'll look at that again; the two behaviors: > 1) waiting for and reaping the exit value us

Re: JEP 102 Process Review

2015-03-24 Thread Roger Riggs
Hi Chris, Thanks for the review and comments. On 3/24/2015 10:42 AM, Chris Hegarty wrote: Roger, I think the API is looking much better now ( just a few comments below on small specific issues ), so I’ve taken a pass over the implementation changes in the sandbox. Here are some comments: 1)