[ https://issues.apache.org/jira/browse/JAMES-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818431#comment-17818431 ]
Benoit Tellier commented on JAMES-3999: --------------------------------------- This is less a priority. We diagnosed the notification issue that lead to this ticket to be caused by a deployment issue. In short we relied on specific instances: some nodes are doing JMAP, some others IMAP/SMTP. IMAP/SMTP nodes were not applying the JMAP listeners leading to resynchronisation issues (it was not "just" a timing issue). However for better JMAP compliance getting a "synchronous" behaviour on /changes is a desirable behaviour for better JMAP compliance. This had been requested by Daniel Glutch (ltt.rs) cketti (k9 + thunderbird) and Mail Temi. I still need to wrap my head around this and propose a patch. > Listener: define priority and apply priority > -------------------------------------------- > > Key: JAMES-3999 > URL: https://issues.apache.org/jira/browse/JAMES-3999 > Project: James Server > Issue Type: Improvement > Affects Versions: 3.8.0, 3.8.1 > Reporter: René Cordier > Priority: Major > Fix For: 3.9.0 > > > Some listener should be executed quicklier than others. > This is paramount to ensure best effort upon resynchronisation. > The idea would be to prioritize in the execution order listeners that have a > higher priority to avoid causing delays. > JMAP listener especially (EmailQueryView, MailboxChange) should be executed > with the highest priority possible. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org