The token contains NO trace info. The CM does. The token is just a key. I use 2 maps because I want BOTH to release single components or all the components for a token. (I want to release "limited" resources like database connections ASAP.)
But keep in mind that only a minority of the used components are usually tracked - since most do not need to be released. Quite a few of my typical requests are processed using several components but not needing to have any of them tracked. A new CM, as light as it might be, ends up creating a few objects and adding an extra wrapping layer. I just think that it does not pay its own overhead. Have fun, Paulo > -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > Sent: Sunday, February 17, 2002 9:24 PM > To: Avalon Developers List > Subject: Re: [VOTE] RE: ComponentManager interface > > > On Mon, 18 Feb 2002 07:26, Paulo Gaspar wrote: > > I believe it is heavier to create a new wrapper CM > > and having another layer than doing it this way. > > (At least for the way I use it.) > > Are you sure? The CM could be just a lightweight object that > contains trace > information about which components have been requested. The token > object of > your way will most likely contain a similar trace - except > because you can > have multiple tokens in progress your way actually is more heavyweight (2 > maps vs 1). Or am I missing something? > > -- > Cheers, > > Pete > > *-----------------------------------------------------* > * "Faced with the choice between changing one's mind, * > * and proving that there is no need to do so - almost * > * everyone gets busy on the proof." * > * - John Kenneth Galbraith * > *-----------------------------------------------------* > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
