From: "Berin Loritsch" <[EMAIL PROTECTED]>
> Granted this is a complicated way of doing things, but as always focus on
> the simple stuff first.
Got it.
> Right now in Java land, we have a lookup() and release() cycle for
components
> being looked up. All that is done with the associated LookupManager (AKA
> ServiceManager). However, you probably have already noticed the absense
of
> the release() method in the C# code.
No no.. It is there:
namespace Apache.Avalon.Framework
{
using System;
<...>
public interface ILookupManager
{
object this[string role]
{
get;
}
void Release(object resource);
}
I swear I didn't touched it :-)
> The reason is that I wanted to make the system as unobtrusive to the
client
> (code using a component) as possible. So for the time being, let's focus
on
> the simple (singleton) lifestyle. If we need something else, we can
address
> it then.
Its a noble objective, but are you sure we gonna achieve it? For sure it's
not a good thing the container expect a correct use from the component
consumer, but I don't see another way..
hammett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
