[ 
https://issues.apache.org/jira/browse/MAILBOX-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030555#comment-15030555
 ] 

ASF GitHub Bot commented on MAILBOX-211:
----------------------------------------

Github user chibenwa closed the pull request at:

    https://github.com/apache/james-project/pull/15


> Distributed IMAP notification - distribute mailbox events
> ---------------------------------------------------------
>
>                 Key: MAILBOX-211
>                 URL: https://issues.apache.org/jira/browse/MAILBOX-211
>             Project: James Mailbox
>          Issue Type: New Feature
>            Reporter: Tellier Benoit
>             Fix For: 0.6
>
>         Attachments: james-distributed-event-system.odp
>
>
> The Mailbox event system is limited to one James instance. This means if a 
> user is connected on a server A and if a mail arrives for him on server B, he 
> will not get the notification.
> This means we need to send events to a message queue, so that they can be 
> treated remotely by other James server to send IMAP notifications.
> But we need to be carefull : we must not trigger some Listener : eg : Event 
> must be treated only once by MessageSearchIndex.
> What we can first notice is that Listener that must be triggered only once 
> are Global Listeners, other are per mailbox registered.
> What we just need to do is :
>  
>   - send event in a per mailbox topic ( so that no James server will have 
> scalibility trubbles ). Imap subscription will be listening the topic of the 
> mailbox they are targeting threw the message queue. Global listener are 
> called only once on the server submitting the event.
> Of course I will provide Spring defined beans and optionnal separated classes.
> What do you think of it ? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to