the API in https://svn.apache.org/repos/asf/james/server/trunk/core-library/src/main/java/org/apache/james/mailboxmanager consists mostly of facet interfaces: specific capabilities that a mailbox may possess. though i may prefer alternative designs, IMHO this is a reasonable approach.
IMO it does seem to me suffer from overextension: there are a number of interfaces which group together many other facets. the problem with this design is it results in an overly broad API. to interface to a function, it is not sufficient to implement a small, precise API tightly coupled to that function nor just those abilities that are required. this approach results in an overly coupled system which is not readily extensible i've been wondering whether it might be better to eliminate the extension between facet interfaces opinions? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
