Return-Path: <issues-return-31475-archive-asf-public=cust-asf.ponee.io@mesos.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id E28A4200B51
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon,  1 Aug 2016 21:12:21 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id E0F86160A6C; Mon,  1 Aug 2016 19:12:21 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 5B884160A66
	for <archive-asf-public@cust-asf.ponee.io>; Mon,  1 Aug 2016 21:12:21 +0200 (CEST)
Received: (qmail 95077 invoked by uid 500); 1 Aug 2016 19:12:20 -0000
Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@mesos.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@mesos.apache.org>
List-Post: <mailto:issues@mesos.apache.org>
List-Id: <issues.mesos.apache.org>
Reply-To: dev@mesos.apache.org
Delivered-To: mailing list issues@mesos.apache.org
Received: (qmail 95062 invoked by uid 99); 1 Aug 2016 19:12:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2016 19:12:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 6BFC12C0059
	for <issues@mesos.apache.org>; Mon,  1 Aug 2016 19:12:20 +0000 (UTC)
Date: Mon, 1 Aug 2016 19:12:20 +0000 (UTC)
From: "Joseph Wu (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12993641.1469825945000.190015.1470078740437@Atlassian.JIRA>
In-Reply-To: <JIRA.12993641.1469825945000@Atlassian.JIRA>
References: <JIRA.12993641.1469825945000@Atlassian.JIRA> <JIRA.12993641.1469825945867@arcas>
Subject: [jira] [Commented] (MESOS-5933) Refactor the uri::Fetcher as a
 binary.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Mon, 01 Aug 2016 19:12:22 -0000


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

Joseph Wu commented on MESOS-5933:
----------------------------------

You can do that by scheduling a task :)

One of the motivations behind the URI fetcher is to get rid of the extra binary (harder to maintain and has some odd undesirable behavior in some configurations).  By running the fetcher separately, you'll end up testing a different code path.  This is especially true if the fetcher becomes pluggable.

> Refactor the uri::Fetcher as a binary.
> --------------------------------------
>
>                 Key: MESOS-5933
>                 URL: https://issues.apache.org/jira/browse/MESOS-5933
>             Project: Mesos
>          Issue Type: Improvement
>          Components: fetcher
>            Reporter: Gilbert Song
>            Assignee: Zhitao Li
>              Labels: fetcher, mesosphere
>
> By refactoring the uri::Fetcher as a binary, the fetcher can be used independently. Not only mesos, but also new fetcher plugin testing, mesos cli and many other new components in the future can re-use the binary to fetch any URI with different schemes. Ideally, after this change, mesos cli is able to re-use the uri::Fetcher binary to introduce new image pulling commands, e.g., `mesos fetch -i <path>`.



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