Markus Kühn wrote:
----- Original Message ----- From: "Stefano Bagnara" <[EMAIL PROTECTED]>
To: "James Developers List" <server-dev@james.apache.org>
Sent: Sunday, May 21, 2006 4:18 PM
Subject: Re: James 2.4 and repositories...
The reasoning behind the choice to merge MailRepository to
SpoolRepository and introduce a new MessageRepository instead of
migrating MailRepository to MessageRepository is:
1st. Greater backward compatibility: if we completely refactor the
MailRepository much more "third party" code will become deprecated
2nd. Avoid confusion: MessageRepository will only store MimeMessage
and not the envelope informations of the Mail object. MailRepository
currently store both, so people could expect this to be also true for
a refactored MailRepository.
I won't be confused if you don't change anything, that does not add
functionality.
If there are new/changed interfaces, new names and the code is actually
doing the same as before, it makes it harder and not easier for those
who know the current code.
Markus
Sorry, I don't understand your points.
In fact I'm talking of changes to implement new features (imap).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
