On 1/17/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
from what i can tell from looking at the newer code, you seem to be moving towards a messaging API but the interfaces suffer from the usual faults (too complex, probably unmaintainable going forward).
+1.
ATM you have an inefficient call based API. over time, optimizing this will ensure that the backend become very tightly coupled to the demands of the protocol. this has already happened. for example, a separate backend implementation is required to efficiently support stateless protocols.
+1
of course, anyone who tries to build alternative mailbox implementations outside the james core team is going to be out of luck. every release will need to break those core interfaces to allow more optimization.
+1
i am disappointed that you let me waste time (that i could have spent more valuable elsewhere at apache) outlining designs that you were never going to accept.
I don't think that is the case, it is a group decision.. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
