On Feb 10, 2015, at 12:25 AM, Roger Riggs <roger.ri...@oracle.com> wrote:
> Hi, > > After a protracted absence from working on JEP 102, the updated API draft > provides access to process hierarchies and individual process information; > as permitted by the OS. The relationship between Process and ProcessHandle > is clarified and the security model validated. > > Both Processes and ProcessHandles can be monitored using CompletableFuture > for termination and to trigger additional actions on Process exit. > Information about processes includes the total cputime, starttime, user, > executable, and arguments. > > Please review and comment: > http://cr.openjdk.java.net/~rriggs/ph-apidraft/ > Since i have your source it's easier in some cases if i copy/paste with line numbers: 57 * <p> 58 * A {@link java.util.concurrent.CompletableFuture} available from {@link #completableFuture} 59 * can be used to wait for process termination and execute a task. 60 * The threads used to monitor the process and execute the task are pooled 61 * using a {@link java.util.concurrent.Executors#newCachedThreadPool}. Is that too much impl detail mentioning the use of the cached thread pool? If so seems more of an implementation note than specification. Paul.