Leo Sutic wrote:
>
> (framework.xml)
> "ThreadSafe
>
> The contract with ThreadSafe Components is that both their interface and
> their implementation function correctly no matter how many threads access
> the Component simultaneously. While this is generally a lofty design goal,
> sometimes it is simply not possible due to the technologies you are using. A
> Component that implements this interface will generally only have one
> instance available in the system, and other Components will use that one
> instance."
What was your issue/update here? I did not see any comments about this block.
> (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.
> --- implementing_orig_1.xml Tue Jul 17 13:53:05 2001
Applied, thanks
> --- framework_orig_2.xml Tue Jul 17 13:55:05 2001
Applied, thanks
S/MIME Cryptographic Signature
