[snip]
>
> Ignoring the question of role oriented configuration for a moment, you end
> with the requirement for either (a) the pooled object to be able
> to identity its source pool - which is undesirable, or (b) forcing the
> manager to maintain usage state (i.e. for every lookup - create a usage
> object that associated the pool and the object so that on release the
> object can be released to the correct pool). I have played a little with
> the second option - suffice to say that it is feasible to do this as an
> internal implementation detail of a generated manager.
Have just updated the excalibur/scratchpad content to support Pooled
services along the lines of option (b) above. Have also added backward
compatibility for Composable.
Cheeers, Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
