IFmsAuthServerContext threadsafeness?

Question

I'm working on a authorize plugin for FMIS, and i'm wondering
if I need to be worried about threads etc when calling
IFmsAuthServerContext's onAuthorize/onNotify from other threads
inside my plugin (ie a thread pool, like the File plugin
example)?

Answer 1

No - it is not even slightly Thread safe. Completely
unsafe, in fact. You don't synchronize
anywhere.Hashtable has synchronisation.
>
The point behind something being Threadsafe is that as
one thread has finished executing one line, and before
it is executing the next, another Thread may have
changed the state of your object. eg.
if (dyn == null) {
//oh-no, another Thread has just loaded the dyn
n variable, if I read dyn now it wouldn't be nullI don't get this. The dyn is a local variable. Every thread has it's own dyn.
dynamicCache.put(intID, Boolean.FALSE);
//even worse, I've just over-written it, and now the
e other Thread is mysteriously getting back FALSEI assume that hashtable still has synchronization.
dyn.loadDynamicByID(id);
dynamicCache.put(intID, dyn);
//oh no, another Thread has just overwritten this
s because it isn't Thread-safe.
Don't mess aroundI'm not.
synchronized (dynamicCache) {
Dynamic dyn = dynamicCache.get(intID);
if (dyn == null)
dynamicCache.put(intID, loadDynamicByID(id));
}Don't try simple Double-checked-locking (DCL doesn't
work in the current Java memory model - see
http://www.javaworld.com) and Thread-local DCL is at
the moment still slower than full synchronization.The idea was to allow multible record loads at the time, but reach specially if the same record is loaded same time. The harddisk access is synchronized with Object hdAccess=new Object.
I might be wrong, but I still think that my code is threadsafe. Sorry for asking help and then arguing, but i do. Point to me that i'm wrong...