Eugene Kuleshov wrote: > > Nat, the package name org.terracotta.annotations (or something like > that) would be the name space, so it could be sufficient to get an idea > about context. > > The whole idea of annotations that they are context specific, so > org.terracotta.annotations.Portable is somehow meaningful on its own. I > initially used "Included" or "Clusterable" annotation, but then recalled > that DSO trows "non-portable" exception, hence @Portable annotation. >
Agreed, though in this case I think it'd be nice to have some context without looking at includes but perhaps that is just personal preference. Personally I think a "ClassNotClusterableException" would mean a lot more at first glance than a "NonPortableException" to an application developer -- my email was mostly a suggestion that we rethink exactly these names since they will be visible in application code and need to make sense to people other than DSO developers. I like 'Clusterable' too :) Nat _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
