Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jslive@gmail.com designates
 66.249.82.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=aaIXh9XseQtJv/tG0dJtBC/rvW5DPKPZ8SEeDoWO0dxX0O24sPEZZ4DhJIgR/zYVjGiv9uK0uF4Su77KeKBUkxHiHelTL4qdGxxKotMtNgdT8ZBtYv8jd87MvKbg5RK8wWysiokwCRhI/GddCjU+rsR8xUgIjXX1FkMF6c+l98w=
Message-ID: <e498c1660606070607k22626486n28f216295359da3b@mail.gmail.com>
Date: Wed, 7 Jun 2006 09:07:42 -0400
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: "Noel J. Bergman" <noel@devtech.com>
Subject: Re: Maven Repo Woes - Temporary resolution in place
Cc: dev@geronimo.apache.org, infrastructure@apache.org,
	"Matt Hogstrom" <matt@hogstrom.org>
In-Reply-To: <NBBBJGEAGJAKLIDBKJOPOEPCIIAC.noel@devtech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <e498c1660606061650u46f90ad2y915ad5c9c1ae3f2@mail.gmail.com>
	 <NBBBJGEAGJAKLIDBKJOPOEPCIIAC.noel@devtech.com>

On 6/6/06, Noel J. Bergman <noel@devtech.com> wrote:
> Joshua Slive wrote:
>
> > So you not only have your build process tied to apache infrastructure
> > in a non-scalable way
>
> Is this the issue with Maven not handling redirects, or something else?

It is the fact that builds of geronimo must download artifacts from
people.apache.org.  We have worked very hard with other projects to
make sure that all downloads point to the mirror system.  Otherwise,
our bandwidth requirements would be many times what they currently
are.  geronimo is circumventing this system.

>
> > but you are essentially doing a DoS attack against the
> > infrastructure every time you build.  Great.
>
> Is this related to anything other than the scalability issue?

Making >10 connections per client to the server is "very bad
behavior", although I was being a little dramatic calling it a DoS.
If more than a few clients at a time were doing this, it certainly
would have an adverse effect on our service.  This is a different
issue than the use of non-mirrored infrastructure for downloads.

Joshua.