I don't see the extra value of adding such package names. I know they are frequently used in other mmbase packages, but it only tells that the next substring in the package is a name for a set of classes which implement functionality (interfaces). Subpackages are always narrowing down functionality and implement something from the super. Adding the long word "implementations" does not make that more explicit.
Pioossibly, except now there wre two places with classes in the clustering package: the core and the clustering application.
That can potentially be confusing.
Also, if other packages use this approach, it would be consistent to use it everywhere.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Anything worth doing is worth overdoing." _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
