Peter Donald wrote: > > On Wed, 10 Jul 2002 20:30, Carsten Ziegeler wrote: > > > It is unfortunate that ECMs lookup is costly. Does Fortresss have > > > this problem > > > aswell? Most containers I work with are little more than a hashlookup. > > > > Even if the lookup is not costly, what about non ThreadSafe components? > > For example the XSLTProcessor is configured to not use the Store, > > the Store would be Poolable (as the XSLTProcessor is) and the > XSLTProcessor > > looksup a Store in compose(). > > So each XSLTProcessor component would block a Store component, although > > this would not be necessary. > > true. But XSLTProcessor would bugger up all those components now > as I removed > the release() ;) > > I looked at all the store implementations and they all were > threadsafe and I > applied the same logic as I did wrt the XMLizer/Parser. ie If all > implementations are threadsafe then dont worry about releasing > the component. > > If the component was poolable then what I did would not be good - > it would > suck actually ;) > Yupp :)
Ok, I totally agree with you that if I know that the component is ThreadSafe, your solution is OK. But I repeat my message from some weeks ago: the client should not know anything about if the used component is thread safe or not. But that's (only?) my opinion. So, keeping it short: you won ;) Carsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
