Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2FEE210F40 for ; Mon, 28 Oct 2013 10:24:15 +0000 (UTC) Received: (qmail 11707 invoked by uid 500); 28 Oct 2013 10:24:14 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 11194 invoked by uid 500); 28 Oct 2013 10:24:14 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 11186 invoked by uid 99); 28 Oct 2013 10:24:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Oct 2013 10:24:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of webdoublefx@hotmail.com designates 157.55.2.98 as permitted sender) Received: from [157.55.2.98] (HELO dub0-omc4-s23.dub0.hotmail.com) (157.55.2.98) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Oct 2013 10:24:05 +0000 Received: from DUB404-EAS148 ([157.55.2.72]) by dub0-omc4-s23.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 28 Oct 2013 03:23:44 -0700 X-TMN: [Z/kRIZza6101zZgdYlquk/tAp/XVUdGp] X-Originating-Email: [webdoublefx@hotmail.com] Message-ID: From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= To: References: In-Reply-To: Subject: RE: Add Mavenizer functionality to Installer Date: Mon, 28 Oct 2013 11:23:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQABAgMEYRToDw/0UWqJlL372Jo6yADWYurGAMAKOG0AdqhzZAAcKqJ8AP/d1GgAbcfhsABeeeEFAFjH/moAtal7MgABI9DMALd1eZCdd6ar0A== Content-Language: fr X-OriginalArrivalTime: 28 Oct 2013 10:23:44.0825 (UTC) FILETIME=[C8081A90:01CED3C7] X-Virus-Checked: Checked by ClamAV on apache.org Justin, If I calculate well, the VM should be able to serve up to 2000 Flex/AIR = SDKs a month, maybe a bit less, depending how much time the CPU will be used = in the month, I added another HDD to secure the data, it has a cost too, = once the build script will be done for the nightly builds and one month of = run, I'll be able to estimate more accurately how many SDKs it can serve. -Fred -----Message d'origine----- De=A0: Fr=E9d=E9ric THOMAS [mailto:webdoublefx@hotmail.com]=20 Envoy=E9=A0: lundi 28 octobre 2013 10:17 =C0=A0: dev@flex.apache.org Objet=A0: RE: Add Mavenizer functionality to Installer Hi Justin, >What to stop users sharing that URL and/or user credentials around? I thought about it too and ended to think I don't want to add more restrictions than what exists today, I mean today, once you accepted a license and downloaded an Adobe Artifact, you can share it as you like, that's not even nominative. I just want to replicate the actual security, so, yes, if an user wants = to share the credentials, it can do it, as it can do it with the artifact itself. > As long as you make it clear that these are not official releases and=20 > for development use only as per Apache policy. Np, it will be suffixed with "-SNAPSHOT " with means in Maven, = non-released > Could it cope with it load and the costs that is likely to incur=20 > (assume 100 or 200 installs a day)? Who owns and maintains the server? Could the apache Flex PMC be given access to it? >From what I understand, I'm not charged or should be very low rate, I = will verify anyway, can't do it now, windowsazure has a 401. I own and maintain the server, it is the same kind than the Erik ones, = it will serve me for some of my devs too (probably) or / and to test the = SDK RCs and I can give access to PMCs who ask me. Thanks, -Fred -----Message d'origine----- De=A0: Justin Mclean [mailto:justin@classsoftware.com] Envoy=E9=A0: = lundi 28 octobre 2013 10:03 =C0=A0: dev@flex.apache.org Objet=A0: Re: Add = Mavenizer functionality to Installer Hi, > From the Installer, users already have to accept licenses for the=20 > third party artifacts, for those users I can grant access to a online=20 > maven repo which serves the Mavenized SDKs What to stop users sharing that URL and/or user credentials around? > I can even add the lasts nightly mavenized build versions. As long as you make it clear that these are not official releases and = for development use only as per Apache policy. > The server exist today as it serves me, it serves up to the 4.11=20 > version Could it cope with it load and the costs that is likely to incur (assume = 100 or 200 installs a day)? Who owns and maintains the server? Could the = apache Flex PMC be given access to it? Thanks, Justin