Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of shane.isbell@gmail.com
 designates 66.249.82.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=lpj2xwmopbysL9k3MDSYg8UkL6RQ8kU4rFytnz7yzU1az0IlV3mRNn3BcbhOuzqE+HgmLRdnsMIEyRfy13tf1rwpdpjuT7SAVMVjJz0NrEUBlWbsUZY6CfsYvoRw2upyt/192aB+h0AoPKGSwwy4A0JtD+54O+gY3HmiZOkZNbI=
Message-ID: <f7743e090705151403r62b9f321o5549b8189fe58b84@mail.gmail.com>
Date: Tue, 15 May 2007 14:03:51 -0700
From: "Shane Isbell" <shane.isbell@gmail.com>
To: general@incubator.apache.org
Subject: Re: [POLL] Incubator Maven Repository
In-Reply-To: <NBBBJGEAGJAKLIDBKJOPMEBIOKAC.noel@devtech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_6560_28111146.1179263031337"
References: <f7743e090705150957s2e82fd1bo657db173f0169d79@mail.gmail.com>
	 <NBBBJGEAGJAKLIDBKJOPMEBIOKAC.noel@devtech.com>

------=_Part_6560_28111146.1179263031337
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Noel,

Correct, using a URI does not require a specific implementation; but in
today's environment, if someone needs a different repo format, they get one
of two responses: 1) create your own repo that uses a different repo format;
or 2) use the same repo format but transform the artifact names. Thus,
the repos - as they exists within the community - are, for all effective
purposes, implementation specific: none of them can be used for custom
formats. Thus the API is adequate, but the implementation may prove
problematic in the long run. I decided to go with option 2; but the point is
that this issue will keep coming up as developers add new languages and
require new formats.

Regards,
Shane


On 5/15/07, Noel J. Bergman <noel@devtech.com> wrote:
>
> > Although HTTP GET with a URL may qualify as an API, under its
> > current form its really implementation (file-system) specific.
>
> What makes it implementation specific?  You can't store the files in a DB,
> and map the URI to the resource?  Isn't it really a URI, specifying the
> package name and version?
>
>        --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

------=_Part_6560_28111146.1179263031337--