Berin Loritsch wrote:
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.
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.
Ummm - so how are you managing the actual release of components? Even if a component is a singleton, the container can track usage based on release notifications by consumers and determine if the singleton component can be decommissioned.
It would be more of a garbage collection process so to speak. Granted, with the use of proxies, the proxy would have to be smart enough to block until the backing component was loaded in...
Nevertheless, since C# is a new effort, Let's worry about the front side first.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
