> One caveat is currently the DefaultElement implementation uses lazy creation
> somewhat to minimise object construction so as 2 threads were to
> concurrently navigate the same document then concurrent modification may
> actually occur in the implementation which might cause a problem.
>
> So we should make a non-lazy implementation of Element for use in
> multi-threaded modes. Also a SynchronizedElement would be useful too. I'll
> add these developments to our to do list...
Ouch! This is very good to know. I've just put integration with Quick's OCM package on
hold until a read-only document can be shared
across threads. (OCM shares its data model across threads. Its intended for both
client and server-side data transformations.)
Not a problem, really. We've pleanty of other work. And fortunately digital signatures
are not yet on our critical path.
Bill
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-user
