> My personal opinion - never - I'm basically of the opinion that a > container should not pool components - instead if want pooled components > then declare a service specific pool and handle this explicitly. But > others may disagree with this conclusion.
Yeah I agree with you Steve. I don't even think we should have this release() method in the service manager. I think it hints of pooling resources. Framework should do way with it in my opinion. Here are some reasons why: 1). The service manager interface is there to manage dependencies that is its sole role and to grant access to these dependent services. 2). The release method makes it look like other services cannot get a handle on the service when this is not the case. We are confusing and bluring the responsibility of the service manager here be presuming some sort of pooling to take place. 3). No one really uses it. 4). There's alot of container specific behavoir that will effect it and not all containers will have lifestyle support. Why not just use another lifecycle method to differentiate the pooled component lifestyles? Bottom line is release makes me think that I'm locking down service instances for exclusive use when in fact I'm not. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
