> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> Sent: den 17 juli 2001 14:26
> To: Avalon Development
> Subject: Re: [Patch] New Avalon Docs
>
>
> Leo Sutic wrote:
> >
> > (framework.xml)
> > (...)
> What was your issue/update here? I did not see any comments
> about this block.
None at all, I just included it as a contrast to the text in
implementing.xml.
> > (implementing.xml)
> >
> > "org.apache.avalon.framework.thread.Threadsafe
> >
> > Component does not maintain state between method calls,"
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > I do not see this as being a necessary part of the contract.
> This would mean
> > that a component that maintains state can not implements its
> own locking and
> > mark itself ThreadSafe.
>
> When I wrote that, I was thinking of an interface like SAX.
> There is a specific
> sequence of method calls, and not context/session object to pass
> to each method.
> In instances like that the interface precludes ThreadSafe
> operation. Do you have
> clearer text that makes that obvious.
- Component is required to serialize access to shared resources.
- Component will not receive any context/session objects, as it is shared
among different contexts/sessions.
Besides that, your point that:
- One instance is created and shared with all Composables that request it.
is enough.
And one more thing:
org.apache.avalon.excalibur.pool.Poolable
- Not thread-safe, but is fully reentrant.
A component whose methods are all fully reentrant is by definition
thread-safe.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
