I have no problem with either... I guess which we go with depends on how likely we thing it is that a third party decides to implement our API.
Chris On Jun 3, 2010, at 11:31 AM, Geert Bevin wrote: > So you're ok with TerracottaReadWriteLock? > > On 03 Jun 2010, at 17:29, Chris Dennis wrote: > >> There's nothing nothing TC specific about the exposed methods, but >> there are many TC specific things in the implementation... although >> this would mean a third party implementor of the API would find it a >> bit odd naming a class Terracotta* we have already crossed that >> bridge >> with other classes (e.g. TerracottaLock). > > -- > 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
