Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 99119 invoked from network); 22 Jun 2002 15:35:14 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 Jun 2002 15:35:14 -0000 Received: (qmail 27509 invoked by uid 97); 22 Jun 2002 15:35:20 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 27493 invoked by uid 97); 22 Jun 2002 15:35:20 -0000 Mailing-List: contact avalon-dev-help@jakarta.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 avalon-dev@jakarta.apache.org Received: (qmail 27481 invoked by uid 98); 22 Jun 2002 15:35:19 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D149858.3020604@apache.org> Date: Sat, 22 Jun 2002 17:31:36 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: What is Avalon? References: <5.1.0.14.2.20020622145742.00ba9600@mail.optushome.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Peter Donald wrote: > At 01:12 AM 6/21/2002 +0200, you wrote: > > However I am not part of the cocoon community and there is little I can > do that will make you realize that violating SOC is bad. I really hope > Leo implements his ideas soon because I am sure that once he has > implemented it he will find out how insane it it is to merge the notion > of resource manager and directory service. I suspect he will also be > wishing for separation of metainfo sooner rather than later. You know darn well that we all know that violating SOC is bad. :-PPP > However while people still insist that mixing concerns is a good thing > then I doubt there can be just one container. IMHO it's more because some of us don't see the solution praticable, while instead it may be. If we stick to concrete examples and code, I'm sure this discussion will go far. When the /hints/ battle started, I thought "Oh no, they want to take functionality away!". I was wrong, but I didn't realize that the discussion was not on wether that functionality would remain, but how it was to be done. > It would be an absolutely fantastic thing to have one though. I'm happy you say it, and agree totally. I *strongly* think we should go in this direction. >> But how do you make them use Avalon? by giving users functionality! >> >> and what is the best functionality if not the ability to reuse prebuilt >> components and create your own? > > This would be fantastic. There are several bits of cocoon already in > excalibur that I would love to be able to use (monitor, xml stuff, > sourceresolve stuff) and I know it would be a very very big draw card if > I could use them un-altered. However I haven't been able to use them > except by changing them in ways that would break them in context of cocoon. :-/ Me too. This reuse-but-not-quite situation *sucks* *big* *time*. Let's make reuse a reality. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: