Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Wed, 21 Sep 2016 16:25:20 +0000 (UTC)
From: "Joerg Schad (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12954912.1459418056000.628548.1474475120607@Atlassian.JIRA>
In-Reply-To: <JIRA.12954912.1459418056000@Atlassian.JIRA>
References: <JIRA.12954912.1459418056000@Atlassian.JIRA> <JIRA.12954912.1459418056790@arcas>
Subject: [jira] [Commented] (MESOS-5070) Introduce more flexible subprocess
 interface for child options.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 21 Sep 2016 16:25:22 -0000


    [ https://issues.apache.org/jira/browse/MESOS-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510435#comment-15510435 ] 

Joerg Schad commented on MESOS-5070:
------------------------------------

The current state is that they only work on linux (windows also ignores the explicit options right now and as you pointed out does not care about parentHooks).

If we are are talking about adding windows support in the future childHooks have one advantage over parentHooks in my opinion:
While parentHooks can be arbitrary functions, childHooks are constrained (via the factory methods) to a small set of predefined hooks -to which we could add some form of id and enable windows to implement its own version of it-.

Maybe [~jieyu] can add more details here.


> Introduce more flexible subprocess interface for child options.
> ---------------------------------------------------------------
>
>                 Key: MESOS-5070
>                 URL: https://issues.apache.org/jira/browse/MESOS-5070
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Joerg Schad
>            Assignee: Joerg Schad
>              Labels: tech-debt
>
> We introduced a number of parameters to the subprocess interface with MESOS-5049.
> Adding all options explicitly to the subprocess interface makes it inflexible. 
> We should investigate a flexible options, which still prevents arbitrary code to be executed.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)