Return-Path: Delivered-To: apmail-archiva-dev-archive@www.apache.org Received: (qmail 5261 invoked from network); 18 Feb 2011 00:57:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Feb 2011 00:57:48 -0000 Received: (qmail 52435 invoked by uid 500); 18 Feb 2011 00:57:48 -0000 Delivered-To: apmail-archiva-dev-archive@archiva.apache.org Received: (qmail 52323 invoked by uid 500); 18 Feb 2011 00:57:47 -0000 Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@archiva.apache.org Delivered-To: mailing list dev@archiva.apache.org Received: (qmail 52314 invoked by uid 99); 18 Feb 2011 00:57:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 00:57:47 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.210.170] (HELO mail-iy0-f170.google.com) (209.85.210.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 00:57:39 +0000 Received: by iyb39 with SMTP id 39so3773726iyb.15 for ; Thu, 17 Feb 2011 16:57:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.177.137 with SMTP id bi9mr105256icb.275.1297990638252; Thu, 17 Feb 2011 16:57:18 -0800 (PST) Received: by 10.42.219.69 with HTTP; Thu, 17 Feb 2011 16:57:18 -0800 (PST) In-Reply-To: References: Date: Thu, 17 Feb 2011 19:57:18 -0500 Message-ID: Subject: Re: Considering Porting Archiva to Google App Engine From: Jarrod Roberson To: dev@archiva.apache.org Cc: Brett Porter Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Feb 17, 2011 at 7:38 PM, Brett Porter wrote: >> Is anyone else interested in something like this? > > I think this would take a bit of work, but I'd be interested to see if the abstractions on trunk for repository storage help to make this possible. > > If you're looking for a simpler solution you might want to try running it on EC2... I've done that quite successfully. Unfortunately EC2 cost more money that I am willing to commit for my use case