Hmm, interesting idea, especially that 2.0.0 is baselined on Java5.
How would such objects be loaded into the cache in the first place?
Perhaps just the initial modification (creation of the object in
cache) and thereafter treated as immutable?
Cheers,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 14 Nov 2006, at 16:06, Julien Viet wrote:
have you ever though about having a way to tell to the optimistic
locking that an object is immutable in order to avoid unnecessary
copies ?
like
public interface Immutable { }
that an object could implement as a marker interface
and
@Immutable
that an object could be annotated with
Julien Viet
JBoss Portal Project Lead
Red Hat Inc.