Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 97153 invoked from network); 28 Oct 2002 22:12:32 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 28 Oct 2002 22:12:32 -0000 Received: (qmail 19492 invoked by uid 97); 28 Oct 2002 22:13:27 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 19476 invoked by uid 97); 28 Oct 2002 22:13:27 -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 19464 invoked by uid 98); 28 Oct 2002 22:13:26 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DBDB652.60204@apache.org> Date: Mon, 28 Oct 2002 23:12:34 +0100 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Avalon Developers List Subject: Re: Avalon Containers References: <002c01c27eca$a1e099e0$6501a8c0@LEIBNIZ> 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 M. Goldstein wrote: >Folks, > >Can anyone point me to a quick discussion of the assorted Avalon >containers? I'd like to see something that has the status, the >development goal(s), and a short list of supported features for each >container. Does such a doc exist? If not, could someone write up a >quick summary? Either a reference or a reply would be greatly >appreciated. Thanks. > Peter: There is a summary of the difference between the different contains on the Merlin FAQ. http://jakarta.apache.org/avalon/excalibur/merlin/faq.html In terms of Merlin future direction - immediate work is focussing on service distribution (connecting a somponents in one container with services resident in another container executing in a different system). Beyond that there will be additions to enable ComponentManager/ServiceManager lookup policy customization which will enable Merlin to complete handle the semantics implied by the ECM/Fortress lookup model. Beyond that - there is strong interest in the delivery of a component packaging model - something more fin grained by the Phoenix SAR file - more like container configuration packaged to go so that we can start using relatively complex component/service assemblies as reusable service modules. Cheers, Steve. > > >--Peter > > > > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: > > > > > -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@osm.net http://www.osm.net -- To unsubscribe, e-mail: For additional commands, e-mail: