Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 46077 invoked from network); 12 Jun 2002 13:37:12 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Jun 2002 13:37:12 -0000 Received: (qmail 15390 invoked by uid 97); 12 Jun 2002 13:37:13 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 15374 invoked by uid 97); 12 Jun 2002 13:37:13 -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 15354 invoked by uid 98); 12 Jun 2002 13:37:12 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) From: "Leo Sutic" To: "'Avalon Developers List'" Subject: RE: [Summary] Avalon 5 ComponentManager interface Date: Wed, 12 Jun 2002 15:36:58 +0200 Message-ID: <007e01c21216$3ae594a0$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 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <1023888894.1874.104.camel@lsd.bdv51> Importance: Normal X-OriginalArrivalTime: 12 Jun 2002 13:37:08.0527 (UTC) FILETIME=[3F9783F0:01C21216] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Leo Simons [mailto:leosimons@apache.org] > > > + All implementations must be thread safe. > > thought: in a simple singlethreaded use of the framework, > thread safety is not something to be concerned about. It'd be > nice to not require a lot of work in this kind of setup. > Should be possible. I'm fine with that. > > + A XXXXManager interface and a corresponding implementation is > > needed for each type 2 and 3 component == more code to write. > > yup, but that code can be within avalon == all but completely > transparant to component developer. Right? Something like what I described to Carsten? I figure that is what will happen, too. The need is so obvious. /LS -- To unsubscribe, e-mail: For additional commands, e-mail: