only one - not only one thread local
[Posted for a colleague]
Hello,
can anyone explain, how the org.apache.avalon.framework.thread.ThreadSafe marker interface modifies the instantiation handling for classes derived from org.apache.cocoon.components.modules.input.AbstractInputModule ?
Does Cocoon ensure that only one thread local instance is running ? And if so, does cocoon cache/pool such module instances so that they don't have to be configured again ?
if a component is thread safe it means every thread can use the same instance - no need for pooling.
If looking for analogy the component works the same as static methods do.
-- Leszek Gawron MobileBox [EMAIL PROTECTED] http://www.mobilebox.pl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
