You should use the MailboxPath for resolve the ACLs.

Where you need to inject the resolver depends on the needs. But I guess you 
need it in both..

Bye
Norman

Sent from my iPhone. Excuse any typos....

Am 06.01.2012 um 14:18 schrieb Jochen Gazda <gazdahims...@gmail.com>:

> Norman,
> 
>>> 8. Interpretation of ACLs:
>>> To have ACL stored on every mailbox is far from being able to tell if
>>> the given user can perform the given operation for the given
>>> mailbox(es when copying/moving).
>>> A new service responsible for resolving of ACLs is necessary. I
>>> propose to call it MailboxACLResolver.
>>> In which package should it be placed? Also in org.apache.james.mailbox?
>>> Probably every single operation between IMAP and mailbox stores should
>>> pass through this service. Where in the code should such a permission
>>> enforcement be placed?
>>> How should MailboxACLResolver be instantiated?
>> 
>> Yeah mailbox api I think… It should be instanced once and get injected in 
>> the constructor.
> 
> Hmmm... I thought that MailboxACLResolver would offer a method like
> the following:
> 
>  boolean hasRight(User user, Mailbox mailbox, Right right);
> 
> But org.apache.james.mailbox.store.mail.model.Mailbox is not visible
> in in mailbox-store. Should I place MailboxACLResolver to
> mailbox-store? Or I should rely on
> org.apache.james.mailbox.MailboxPath rather than Mailbox itself?
> 
>> [MailboxACLResolver] should be instanced once and get injected in the 
>> constructor.
> 
> Which constructor? MessageManager or MailBoxManager or both?
> 
> Best,
> 
> Gazda
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
> For additional commands, e-mail: server-dev-h...@james.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Reply via email to