On Wed, May 19, 2010 at 5:31 PM, Geert Bevin <[email protected]> wrote:
> This is the current hierarchy for the app dev (the TIM dev has other > appropriate types also): > > org.terracotta > api > ClusteringProvider > cluster > TerracottaCluster > TerracottaClusterEvent > TerracottaClusterListener > TerracottaClusterTopology > TerracottaNode > UnclusteredObjectException > collections > MapSizeListener > TerracottaMap > coordination > Barrier > locking > FinegrainedLock > LockableMap > LockStrategy > LockType > ReadLock > ReadWriteLock > TerracottaLock > WriteLock > logging > TerracottaLogger > properties > TerracottaProperties > util > TextBucket What about moving collections, coordination and locking packages into the api package, and renaming util package in "support" (it doesn't seem something users will actually use)? Regarding TerracottaMap, how will users access it? -- Sergio Bossa http://www.linkedin.com/in/sergiob _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
