Hi,
I have some question on the ExcaliburComponentManager.
As it seems to me it behaves like the following if I implement the LifeStyle interfaces ThreadSafe or Poolable:
1) I will get back an instance that may have been used before.
2) LifeCycle is managed when requesting the object (first time).
3) Pool is filled up on first request.
Maybe it is some kind of caching, but can't 2) and 3) be done already when initializing the ECM (thinking of performance)?
If 1) is correct, I don't get the meaning of recycable as I will reuse the same instance anyway.
Thanks, Michael
----------------------------------------- (on the network) ********************************* PRIVILEGED - PRIVATE AND CONFIDENTIAL This e-mail and files transmitted with it are intended solely for the use of the addressee(s) and may contain information which is confidential or privileged. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you receive this e-mail and you are not the addressee, or you have received this e-mail in error, please disregard the contents of the e-mail, delete the e-mail and notify the author immediately. *********************************
---------------------------------------------------------
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
