You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Th...@gfk.de on 2005/04/13 16:55:18 UTC
ThreadSafe Marker On InputModules?
[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 ?
Thanks anyway for your superior support,
Sebastian
_________________________
Diese E-Mail (ggf. nebst Anhang) enthält vertrauliche und/oder rechtlich
geschützte Informationen. Wenn Sie nicht der richtige Adressat sind, oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die
unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail (and any attachment/s) contains confidential and/or privileged
information. If you are not the intended recipient (or have received this
e-mail in error) please notify the sender immediately and destroy this
e-mail. Any unauthorised copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.
_________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ThreadSafe Marker On InputModules?
Posted by Leszek Gawron <lg...@apache.org>.
Thomas.Zirnsack@gfk.de wrote:
>
>
>
> [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 ?
only one - not only one thread local
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
lgawron@apache.org http://www.mobilebox.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org