[jdom-interest] Thread safe question: OK for simultaneous read-only access?
szegedia at freemail.hu
Tue Oct 30 02:03:19 PST 2001
They can, but that will be less elegant as every wrapper object will have excess baggage in form of fields it inherits from its respective JDOM superclass and which it ultimately does not need. My previous post focused on elegance of possible wrapper implementation, and didn't question the possibility of wrapper implementations in general.
----- Original Message -----
From: <philip.nelson at omniresources.com>
To: <szegedia at freemail.hu>; <jdom-interest at jdom.org>
Sent: 2001. október 30. 2:36
Subject: RE: [jdom-interest] Thread safe question: OK for simultaneous read-only access?
> Wrappers can be implemented very well without interfaces + default
> implementation. ;-)
> I agree with the general consensus that a JDOM document doesn't need provide
> thread safety. A specific application could subclass the various JDOM
> mutatators it was going to use and syncronize on the Doctype. If the
> Element hadn't been added to a document, it really wouldn't matter much,
> unless you were trying to build your own Lists outside of JDOM. In that
> case, there wouldn't be much we could do anyway.
> -----Original Message-----
> From: Attila Szegedi
> To: jdom-interest at jdom.org
> Sent: 10/29/01 4:51 AM
> Subject: Re: [jdom-interest] Thread safe question: OK for simultaneous
> read-only access?
> I don't know if anyone works on such thing, but one thing that comes to
> mind is that this kind of "wrappers" could be implemented very elegantly
> if JDOM were designed in terms of interfaces + default implementation.
> To control your jdom-interest membership:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2848 bytes
Desc: not available
Url : http://jdom.org/pipermail/jdom-interest/attachments/20011030/e683f872/smime.bin
More information about the jdom-interest