Return-Path: 
 <dev-return-26755-apmail-avalon-dev-archive=avalon.apache.org@avalon.apache.org>
Delivered-To: apmail-avalon-dev-archive@www.apache.org
Received: (qmail 45242 invoked from network); 17 Oct 2003 21:52:46 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 17 Oct 2003 21:52:46 -0000
Received: (qmail 10927 invoked by uid 500); 17 Oct 2003 21:52:31 -0000
Delivered-To: apmail-avalon-dev-archive@avalon.apache.org
Received: (qmail 10830 invoked by uid 500); 17 Oct 2003 21:52:31 -0000
Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@avalon.apache.org>
List-Subscribe: <mailto:dev-subscribe@avalon.apache.org>
List-Help: <mailto:dev-help@avalon.apache.org>
List-Post: <mailto:dev@avalon.apache.org>
List-Id: "Avalon Developers List" <dev.avalon.apache.org>
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Delivered-To: mailing list dev@avalon.apache.org
Received: (qmail 10811 invoked from network); 17 Oct 2003 21:52:30 -0000
Received: from unknown (HELO mail.ibiblio.org) (152.2.210.112)
  by daedalus.apache.org with SMTP; 17 Oct 2003 21:52:30 -0000
Received: from apache.org (e004.dhcp212-198-17.noos.fr [212.198.17.4])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by mail.ibiblio.org (Postfix) with ESMTP id 68EB624ADC7
	for <dev@avalon.apache.org>; Fri, 17 Oct 2003 17:52:36 -0400 (EDT)
Message-ID: <3F90652E.30006@apache.org>
Date: Fri, 17 Oct 2003 23:54:54 +0200
From: Stephen McConnell <mcconnell@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Avalon Developers List <dev@avalon.apache.org>
Subject: Re: [RT] semantic conflict - poolable
References: <000401c394de$33503190$0801a8c0@lagrange>
In-Reply-To: <000401c394de$33503190$0801a8c0@lagrange>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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



Leo Sutic wrote:

>  
>
>>From: Stephen McConnell [mailto:mcconnell@apache.org] 
>>
>>a solid defition of the four "standard" lifestyles.
>>    
>>
>
>I think we already have that. Pooled means one-per-lookup,
>from a common pool, singleton means singleton per container, 
>transient means one new instance per lookup.
>
>Why not just let the definitions stand as they are? I think
>they are clear enough. The words "pooled" and "singleton"
>are well defined. "Transient" is made up here, but if we
>say "one new instance for each lookup()" then I think
>most people will understand.
>

Some questions for you - here is a defintion of a container with two 
components. Lets assume that the component lifestyle is singleton.

<container name="demo">
   <component type="PersonProvider" name="accounts">
     <configuration>
        <name>Sally</name>
     </configuration>
   </component>
   <component type="PersonProvider" name="logistics">
     <configuration>
        <name>Carol</name>
     </configuration>
   </component>
</container>

I've just broken you defintion of a singeton.  My notion of a 
"singleton" lifestyle is that an instance of an identifiable component 
deployment scenario may be shared across all requests - and that 
multiple deployment scenarios may coexist for that type.  In the above 
example - we would see two component managers each differentiated in 
terms of the deployment scenario (different confuration or parameters, 
etc.).

Transient - a new instance per lookup - fine with that.
Pooled - nothing more than a managed transient.
Thread - same as singleton except that is scope with respect to sharing 
is a new instance per thread.

Stephen.

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org