Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 58592 invoked from network); 12 Nov 2003 11:47:28 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 12 Nov 2003 11:47:28 -0000 Received: (qmail 52909 invoked by uid 500); 12 Nov 2003 11:47:27 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 52625 invoked by uid 500); 12 Nov 2003 11:47:25 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 52612 invoked from network); 12 Nov 2003 11:47:24 -0000 Received: from unknown (HELO osm.net) (212.198.17.4) by daedalus.apache.org with SMTP; 12 Nov 2003 11:47:24 -0000 Received: from localhost ([127.0.0.1]) by osm.net (JAMES SMTP Server 3.0a1) with SMTP ID 467; Wed, 12 Nov 2003 12:50:05 +0100 (CET) Message-ID: <3FB21E6D.4020702@apache.org> Date: Wed, 12 Nov 2003 12:50:05 +0100 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en, en-us MIME-Version: 1.0 To: dev@cocoon.apache.org CC: Apache Slide , Avalon Dev Subject: Re: Migrating to Avalon. Thoughts? References: <20031112165941.092143@greystorm> In-Reply-To: <20031112165941.092143@greystorm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Just a note to let you know that there are a number of threads currently running over on the dev@avalon.apache.org concerning the establishment of a component repository project. After reading your email I think that many of the subjects you have addressed below are relevant to the things the Avalon crew are currently debating. Cheers, Steve. Edison Too wrote: >Hi, > >I agree with Stefano's observation that there is a need for a good content repository. I've looked into Slide's code before and I can't help but wonder if it is a good idea for Slide to be implemented using Avalon. > >The server core can be broken down into 3 blocks >1. Content repository (store?) >2. User management >3. Access Control management >These are very useful/essential component which are (AFAIK) strangely missing in the current crop of Avalon Components/Services. > >Advantage of migrating : >1. Reuse of Avalon components such as configuration/connections/pooling/logging etc. >2. Deployable as a standalone or servlet using Fortress or Phoenix. >3. If a Cache block comes along (from Cocoon maybe?) it can be reused in Slide to improve performance. >4. Attract more developers from the land of Avalon or Cocoon. >I think it will open up a lot of possibilities. Think of it, with James, Slide, Cocoon, interesting server apps can be built. > >I know it's not easy to switch and most developers dread such a big change especially when r2.0 is in view. This is just a thought I feel worth discussing, especially when Stefano says he will investing his time into Slide. > >I'm not an expert with Avalon, but I'm willing to invest some time if this the direction Slide decide to pursue. > >Thoughts? > >Cheers, >Edison Too > >On Tue, 11 Nov 2003 16:02:00 +0100, Stefano Mazzocchi wrote: > > >>[copying dev@cocoon because many people are in search for a serious versioned >>content repository these days] >> >>Hello everyone, >> >>I find myself in the need for a serious WebDAV/DeltaV/DASL content repository >>and after having searched land and sea and having tried all possible >>combinations out there [pure mod_dav, catacomb and subversion], I decided to >>use invest my effort in Slide, also because of the familiarity with the java >>language compared to mod_dav which isn't really friendly for me] >> >> >> > > > > > -- Stephen J. McConnell mailto:mcconnell@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org