I'll all for cutting it out of the first release. It still has to be in the toolkit of course but it doesn't have to be exposed to the non-advanced usage (Whatever that is called now -- ExpressToolkit, StandaloneClusteringProvider, etc)
> -----Original Message----- > From: tc-dev-boun...@lists.terracotta.org [mailto:tc-dev- > boun...@lists.terracotta.org] On Behalf Of Geert Bevin > Sent: Wednesday, May 26, 2010 9:14 AM > To: tc-dev > Subject: [tc-dev] DistributedCache exposed in toolkit > > Hey, > > As is stands, the DistributedCache is currently exposed through > TerracottaClient with the > toolkit.getDistributedCacheConfig().newCache() methods. > > Since there have been different opinions on exposing the > DistributedCache class, should we keep this in or only allow framework > developers to use it? > > Thanks, > > Geert > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > > _______________________________________________ > 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
