james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MAILBOX-212) Event bugg upon MailboxRenamed events
Date Fri, 30 Jan 2015 08:07:34 GMT

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

Tellier Benoit closed MAILBOX-212.
    Resolution: Fixed

> Event bugg upon MailboxRenamed events
> -------------------------------------
>                 Key: MAILBOX-212
>                 URL: https://issues.apache.org/jira/browse/MAILBOX-212
>             Project: James Mailbox
>          Issue Type: Bug
>            Reporter: Tellier Benoit
> Hi,
> I am writing a distributed event system for the James mailbox ( so that
> IDLE imap command will work in a distributed environement ). Doing this,
> I am starting to write tests on top of the existing James event system
> and I notice this point :
> Listener per mailbox registration is not updated upon MailboxRenamed events.
> This implies that listeners do not receive any events after a
> mailboxRenamed event (not even this event).
> To solve this, we must trigger MailboxRenamed events in the event loop,
> and :
> - explicitly check from field with these kind of events, and notify clients
> - I do not know if we should still be connected in IDLE after a mailbox
> rename... rfc2177 is  not clear about that,so I don't know if it makes
> sens to change the path listener are listening on (move listeners
> listening to the old path to the new path ).
> But I really think they should be notified about the mailboxRenamed event.
> What do you think of it?

This message was sent by Atlassian JIRA

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

View raw message