On Fri, 11 Jan 2002 02:26, Berin Loritsch wrote: > > BTW, do we dump the Component interface? > > I think that is the general consensus. However I do have one more use for > it: > > If we move the release() method from ComponentManager, and place it in the > Component interface, then Components that require releasing because they > are pooled have a mechanism to do so. That policy should be decided by the > work interface. For example: a component that extends ContentHandler > cannot be threadsafe, so it would implement the Component interface--but a > component that does not need to be pooled by virtue of the work interface > would not implement the Component interface.
I think it should be solely up to the work interface to release the component if the component is actually just a shallow facade ontop of a real resource. For instance close() when used on a JDBC connection would place the real underlying resource back in pool. Similar methods will be used with other resources/components but I don't think we should have a Component interface provide such a method. -- Cheers, Pete -------------------------------------------------- you've made a dangerous leap right over common sense, like some kind of metaphysical Evil Knievel -------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
