Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 8522 invoked from network); 24 Jun 2002 11:09:57 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 24 Jun 2002 11:09:57 -0000 Received: (qmail 8275 invoked by uid 97); 24 Jun 2002 11:10:02 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 8254 invoked by uid 97); 24 Jun 2002 11:10:01 -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 8233 invoked by uid 98); 24 Jun 2002 11:10:00 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) From: "Leo Sutic" To: "'Avalon Developers List'" Subject: [Attn: Leo, Peter, Berin ( + just about anyone else)] Micro/Embedded/Server (was: RE: What is Avalon?) Date: Mon, 24 Jun 2002 13:09:36 +0200 Message-ID: <000601c21b6f$a15335a0$0801a8c0@Lagrange> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <1024911747.2008.37.camel@lsd.bdv51> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-OriginalArrivalTime: 24 Jun 2002 11:09:52.0376 (UTC) FILETIME=[A9CADF80:01C21B6F] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Leo, Peter, Berin, I'll be going full tilt into MicroContainer now. This is my world as I see it: + MicroContainer: Use of Avalon components without the Avalon architecture. What I see before me are three actors: A user: A developer that is doing, well, something. The A component: The user just downloaded this. A deadline: The user hopes to use the component in order to be finished before this. MicroContainer will solve this with minimal impact on the user's architecture. ( MicroContainer is checked in under jakarta-avalon/src/proposal/microcontainer/ ) + Tweety: The simplest stand-alone container. Used to teach people how to write containers without using Fortress. + Fortress: The "embedded" level container. Think "Cocoon". + Phoenix: "Server" level. Uses Fortress. Metainfo is used by Fortress and Phoenix (not MicroContainer). + Anything that works in Micro, works in Fortress, Tweety and Phoenix. + Anything that works in Fortress, works in Phoenix. So, when going to a more sophisticated container, you *never* lose anything. All you get is more features from the container. But, some components may not work in Micro or Fortress (they require Phoenix). Is this sort-of-kind-of the world you are living in? /LS > -----Original Message----- > From: Leo Simons [mailto:leosimons@apache.org] > Sent: den 24 juni 2002 11:42 > To: Avalon Developers List > Subject: RE: What is Avalon? > > > > I have taken steps to improve our branding and marketing, > and I hope I > > can get you and the rest into a discussion regarding > > this: > > > > not necessary =) I agree with it. Now to do the coding... > > - Leo > > > > > -- > To unsubscribe, e-mail: > unsubscribe@jakarta.apache.org> > For > additional commands, > e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: