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
I think that the biggest advantage is that somebody using such a package
knows where to look. The javadocs become clearer. But I don't really
bother for this pakage.
If there is a problem and I need to dive in the code i'ts going to be
in the implementation anyway.
Guess I didn't read your
nico wrote:
Directory /var/cvs/applications/clustering/src/org/mmbase/clustering added to the repository
Noticed that the clustering application was added.
Good show, though I had preferred that the implementations were added
under org/mmbase/clustering/implementations rather than
Pierre van Rooden wrote:
nico wrote:
Directory /var/cvs/applications/clustering/src/org/mmbase/clustering
added to the repository
Noticed that the clustering application was added.
Good show, though I had preferred that the implementations were added
under org/mmbase/clustering/implementations
