> The proposals to do that from Serge and myself are based upon using > JavaMail. JavaMail doesn't provide us with a canonical storage format. > JavaMail provides API and functionality built on top of service providers. > One type of service provider is a storage provider. There are storage > providers for mbox and maildir, for example. Serge proposes that we also > take our existing storage implementations (Avalon repository and JDBC > repository), and adapt those to use the JavaMail service provider > interface. > By using the JavaMail storage interface, we can access any of > those formats. > > JavaMail > | > --------------------------------------------- > | | | | | > mbox maildir Avalon File JDBC store etc. > > In summary, JavaMail facilitates our use of multiple storage formats, adds > functionality that we need on top of those formats, and allows us to > leverage more resources effectively. > > Does this make more sense, now?
Yeah, it does, and it answers my concern too. I'm now +1, on condition all our existing repositories are migrated to javamail. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
