Comments inline.. 2010/8/22 Eric Charles <e...@apache.org>: > one more inline :) > > On 22/08/2010 13:58, Norman Maurer wrote: >> >> Not 100%.. Subscriptions links users to Mailboxes. The users are just >> Strings and nothing more. So its not coupled to james server in any >> way. >> > Yeah, these are "soft links". > A "Subscription store" could be different from the "Mailbox store" (so we > have links via String). > Example: > - Users are stored in LDAP tks to james-server. > - Mailbox in DB via JPA. > - Subscription "soft link" LDAP to DB and these "soft links" are store > "anywhere" defined by the admin (in spring-beans.xml). > >> (snippped...) >> Just as a side-note... For example the subscription stuff is not >> really necessary for using MailboxManager in non-imap enviroments (for >> example pop3). >> > True enough. > I re-read the pop3 case, and I see one more argument to leave the > SubscriptionManager independent of the MailboxManager. > So http://svn.apache.org/viewvc?rev=987821&view=rev "Move the Subscriper to > the mailbox api and rename it SubscriptionManager..." makes all its sense. > > There's still the open question on start/stopProcessing and listener (to be > duplicated in Mailbox/SubscriptionManager or externalized ?). > To take a decision , we should also consider that operations need to be > atomic, so encapsulate the Mailbox/SubscriptionManager processing. > So "externalize/encapsulate" makes some sense, as you communicated me ? >
I don't know yet.. whats you preference ? Bye, Norman --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
