[
https://issues.apache.org/jira/browse/MAILBOX-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285423#comment-14285423
]
Tellier Benoit commented on MAILBOX-64:
---------------------------------------
Yes, things exists to manage quotas directly in the mailbox but I do not really
like it.
In quota managements, I think they are two kind of value we care about :
- the current resource values
- the maximum policies for these values
The fact is that we may want different things :
For instance storing max policies in RAM, in database ( for distributed James )
or even in a LDAP ( what can be done with Cyrus ). You may want global max
policies, per user max policies, or even no policies at all.
For the current resource value, we may want to update a stored value every time
a message is added to the mailbox, and store it in RAM, or in a database. We
may also want to calculate it each time.
That is why I think we should have 3 APIs :
- An API to retrieve current values for Quotas
- An API to retrieve maximum policies for Quotas
- Nowadays QuotaManager, that simply build quota using these API ...
Of course we need to update things defined in store, and I will update
Cassandra's stuff.
I already wrote some code ( APIs, store, and cassandra ) I just need to write
a few tests, and need an internal review at Linagora before submitting it to
you.
> Add out-of-the box support for quotas
> -------------------------------------
>
> Key: MAILBOX-64
> URL: https://issues.apache.org/jira/browse/MAILBOX-64
> Project: James Mailbox
> Issue Type: New Feature
> Components: api, store
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 0.3
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
