> From: Vincent Massol [mailto:[EMAIL PROTECTED]]
>
> Leo,
>
> First thanks for the quick answer.
>
> The problem with our application is that there is a very very strict
> requirement : 99.97% of user requests must not take longer than 1 second
> (it's not a web application and we do control the maximum number of
> users that come in the system, lucky us !).
OK... I would do all my lookups in compose() then, and release them in
dispose().
That brings the ECM totally out of the loop when it comes to processing,
and your code will run at max speed.
That'd be the ideal, right?
> I was wondering really about why we have to use synchronized in
> BucketMap.get().
I think the only risk is a concurrent BucketMap.put that may resize the
map and thus move stuff around. Then again, I might be wrong about this one.
> It seems to me the only reason is for decommissioning
> the components. However, decommissioning is a rare event (which do not
> happen during the whole life of most application). Lets' say I don't
> care about releasing ThreadSafe component; why would I need a
> synchronized block in lookup() ?
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
