Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 33919 invoked from network); 18 Nov 2003 16:18:41 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 18 Nov 2003 16:18:41 -0000 Received: (qmail 4152 invoked by uid 500); 18 Nov 2003 16:18:07 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 4091 invoked by uid 500); 18 Nov 2003 16:18:06 -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 3988 invoked from network); 18 Nov 2003 16:18:06 -0000 Received: from unknown (HELO hqexch01.upstate.com) (205.160.101.145) by daedalus.apache.org with SMTP; 18 Nov 2003 16:18:06 -0000 Received: from IQUITOS (iratcliffe2.group.upstate.com [172.17.1.103]) by hqexch01.upstate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XCTZNYGK; Tue, 18 Nov 2003 11:19:04 -0500 Reply-To: From: "Eric Pugh" To: "'Avalon Developers List'" Subject: RE: [proposal] IoC type 3.14 extension to the Avalon Framework Date: Tue, 18 Nov 2003 17:18:04 +0100 Message-ID: <00c901c3adef$8c449640$0100a8c0@IQUITOS> 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 CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3FBA38E1.3000009@apache.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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 I gotta says, the requirement to use other people's interfaces is a huge roadblock.. I don't wanna (said like a child :-)) use other peoples interfaces, I want to use mine! Hence the appeal of the constructor approach or the very introspection/reflection approaches... Eric > -----Original Message----- > From: Berin Loritsch [mailto:bloritsch@apache.org] > Sent: Tuesday, November 18, 2003 4:21 PM > To: Avalon Developers List > Subject: Re: [proposal] IoC type 3.14 extension to the Avalon > Framework > > > Ulrich Mayring wrote: > > > Jonathan Hawkes wrote: > > > >> Did you even read the rest of the message? I'm not > pushing a type 3 > >> replacement. You could continue to write components as > you wish. Please > >> see the original message and do me the courtesy of reading > it. I'm not > >> trying to spark an argument over which way is best. > > > > > > Sorry to be unclear, I'll try again. I wanted to communicate that I > > don't see the need for type 3 and therefore your proposal. > This does not > > mean that I would -1 it, if I were a committer. It just > means that I > > don't need it and haven't understood why others do :) > > Easy: > > There are developers who simply refuse to use other people's > interfaces > (shocking but true), and to support folks who suffer from NIH syndrome > (Not Invented Here), the constructor mechanism what was come up from. > > It has everything to do with development style, and what some > developers > think is easy others think is a pain. > > That's why I really don't care what method is used to > accomplish IoC as > long as it is supported. > > > -- > > "They that give up essential liberty to obtain a little > temporary safety > deserve neither liberty nor safety." > - Benjamin Franklin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org > For additional commands, e-mail: dev-help@avalon.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org