Well one thing is that Clearable isn't really meant to be particularly user facing at the moment. Only things in the toolkit API are really coming into the public light at this time.
Clearable is used on out logically managed collection classes at the moment. For things like ConcurrentDistributedMap that manage their own faulting/flushing it lets the data structure play nice with the core memory manager that initiates reference clearing. It can also be used to allow specific shared objects to prevent reference clearing. A discussion of Clearable wouldn't be complete without talking about the NotClearable interface. NotClearable lets you exclude an entire type (ie. all instances) from reference clearing. Hope this helps. > -----Original Message----- > From: tc-dev-boun...@lists.terracotta.org [mailto:tc-dev- > boun...@lists.terracotta.org] On Behalf Of Sergio Bossa > Sent: Wednesday, May 19, 2010 11:33 AM > To: tc-dev@lists.terracotta.org > Subject: Re: [tc-dev] Toolkit and custom types for app devs > > On Wed, May 19, 2010 at 8:06 PM, Tim Eck <t...@terracottatech.com> > wrote: > > > I lied (sorta). The Clearable is actually now contained in the new > TIM API > > module (https://svn.terracotta.org/repo/tc/tim-api/trunk/tim-api) > > What's the meaning/usage of the Clearable API from 3.3.0 onwards? > > -- > Sergio Bossa > http://www.linkedin.com/in/sergiob > _______________________________________________ > tc-dev mailing list > tc-dev@lists.terracotta.org > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
