Your summary sounds correct to me.
> -----Original Message----- > From: tc-dev-boun...@lists.terracotta.org [mailto:tc-dev- > boun...@lists.terracotta.org] On Behalf Of Sergio Bossa > Sent: Thursday, May 20, 2010 12:52 AM > To: tc-dev@lists.terracotta.org > Subject: Re: [tc-dev] Toolkit and custom types for app devs > > On Wed, May 19, 2010 at 9:04 PM, Tim Eck <t...@terracottatech.com> > wrote: > > > 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. > > Thanks Tim for your explanation. > Let me see if I've got it right. > So, Clearable is used as an hint to the memory manager for classes > which do their own _explicit_ flush/fault management, so that the > memory manager will call a callback method to perform a custom > cleaning. > NotClearable is used to completely exclude a class (and related > members) from reference cleaning. > Is that right? > > -- > 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
