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).
Chris On Jun 3, 2010, at 11:22 AM, Geert Bevin wrote: > Hi, > > This is the class name that's still bothering be most: > SharedReadWriteLock. It's basically an implementation of > ReadWriteLock that automatically works in clustered or unclustered > mode. Should we rename it to TerracottaReadWriteLock even though > there's nothing TC specific? Any other ideas? > > 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
