Am Freitag, den 05.01.2007, 11:24 +0000 schrieb Danny Angus: > > >> The best way would be a native, logical, hierarchical mailbox access > > >> through the Mailet API. > > > > > > If you would like to expand on this idea I'd be interested in seeing > > > what it looks like when applied to sandbox/mailet-refactorings/. If > > > you want to have a go yourself please do, otherwise talk about it and > > > I'll do something. > > > > > > > But whouldn't this bind the mailet api to james ? Maybe i just not > > understood . Please explain ;-) > > Not necessarily. The mailbox manager interfaces could be moved to the > API, but only if they allow other implementations to easily implement
Right. Especially if we use a reasonable subset. > mailbox manager. however the javadocs do say: > " * An important goal is to be JavaMail feature compatible. That means > JavaMail > * could be used in both directions: As a backend for e.g. accessing a Maildir > * JavaMail store or as a frontend to access a JDBC MailboxManager > * through JavaMail. " > > *if* this is true I can see no reason why we wouldn't benefit from > abstracting access to hierarchical mail storage. JavaMail is probably the more difficult variant. :-) MailboxManager (maybe a subset) and Mailbox (very similar to current MailRepository) should be enough. Of course providing a JavaMail wrapper would be nice for more compatibility. IMO using just pure JavaMail would be not so good for known reasons about using JavaMail, which is a client API, on servers. Joachim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
