You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2021/02/05 05:47:00 UTC

[jira] [Updated] (JAMES-3211) Handle server-data events in order to pre-populate quota ratios

     [ https://issues.apache.org/jira/browse/JAMES-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier updated JAMES-3211:
----------------------------------
    Summary: Handle server-data events in order to pre-populate quota ratios  (was: Extends mailbox-api EventBus interface)

> Handle server-data events in order to pre-populate quota ratios
> ---------------------------------------------------------------
>
>                 Key: JAMES-3211
>                 URL: https://issues.apache.org/jira/browse/JAMES-3211
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Lan Khuat
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When searching for users by quota ratio if we set the value of the parameters to 0 the search feature is supposed to return newly created users who have not received any email yet at that point. However, this is not the case because the quotas are currently being initialized only after a user has received the first email.
> We need to initialize user quotas upon user creation time. The problem is there is currently no event at user creation and since the quota-search feature is a plugin of James, it cannot be hardwired into the domain logic of user management to initialize the quota for a just created user.
> For quota-search to be initialized/removed for a given user while keeping this feature as a plugin, we decided to adopt the Event Driven pattern we already use in mailbox-api. We can create new events related to user management.
> *DOD:*
>  * Extract the EventBus out of mailbox-api in order to make it a utility component (eventbus-api), then mailbox-api and data-api will depend on that new module.
>  * Define a common Event interface in eventbus-api, then each event-bus usage will define its own sealed event hierarchy implementing Event.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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