Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Message-ID: <3F26E184.1030900@apache.org>
Date: Tue, 29 Jul 2003 17:05:08 -0400
From: Berin Loritsch <bloritsch@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Avalon Developers List <dev@avalon.apache.org>
Subject: Re: ROLE & Lifecycles in C#
References: <6485684CCD23CE4FA95B7FA02A2A5C0D18CA3D@EMSS04M12.us.lmco.com>
In-Reply-To: <6485684CCD23CE4FA95B7FA02A2A5C0D18CA3D@EMSS04M12.us.lmco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Geer, Christopher S wrote:

> 
>>-----Original Message-----
>>From: Berin Loritsch [mailto:bloritsch@apache.org]
>>Sent: Tuesday, July 29, 2003 3:54 PM
>>To: Avalon Developers List
>>Subject: Re: ROLE & Lifecycles in C#
>>
>>Yauheny Mikulski wrote:
>>
>>
>>>Hi,
>>>
>>>
>>>
>>>>It makes the contract much more loose and the method >names turn
> 
> into a
> 
>>mess. Right now, if I see a method >named "configure" then I know
> 
> where it
> 
>>fits in.
>>
>>>I agree and suggest the following.
>>>We can implement both variants.
>>>Let people decide what way they should go.
>>>
>>>Personally I got accustomed to the interface model
>>>cause I came to .NET from Java but others ...
>>>
>>>I believe delegate and attribute model is very important as well and
> 
> we
> 
>>shouldn't forget it.
>>
>>>There are pros and cons of every of them.
>>>and I think we might have a long discussion.
>>
>>Let's not make it too long ;P
>>
>>The interface model will work just fine--esp. for interfaces where
>>there is something to pass in.
>>
>>The attribute model would be best for the meta info, and I believe we
>>have already identified a fairly rich set of tags we can include.
>>
>>We might reduce the number of interfaces that we have though.  For
>>example, we could merge Startable and Initializable to just have
>>Initializable and Disposable.  I.e. we should simplify to the easiest
>>thing.
> 
> 
> What is a list of interfaces (and methods) you think should be used? 
> 
> While were on this topic, we should also take a look at renaming certain
> items to not overlap with .NET defined interfaces and methods. (such as
> Disposable or Dispose() methods).

Question about that:

If there is already a IDisposable.Dispose(), then why not use it?  What
context is it used with?  I see no sense in reinventing the wheel.

Short list is:

Configurable
LookupEnabled
Initializable
Disposable

The LookupEnabled would merge the ServiceManager and Context concepts into
one, with a LookupManager.  If there is a .NET equivalent for that, it would
be useful to know.
-- 

"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