Leo Sutic wrote:
>
>>From: Peter Donald [mailto:[EMAIL PROTECTED]]
>>
>>
>>>And this is where I disagree - not having remove requires the client
>>>to know about implementation details such as whether a component
>>>is thread safe or not, whether it is pooled or not.
>>>
>>no it doesn't. It implies that the container has to manage resource
>>allocation and deallocation.
>>
>
> It also implies that CM == container (as it does not expose any method for
> releasing resources) && all requests come in through the CM (otherwise
> it can not know when a request starts/ends), which is not true.
>
> /LS
I sure hope not. The original implementations of CM were simply a wrapper
to map back to the real Container.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
