Hi Eric, Thanks for this reply, I'm only just getting round to QAing this feature, and I had a question: what happens when "new mail" events occur outside James? In my scenario, James is acting as a wrapper for a REST-based message system. Messages arrive on the REST-based backend and then loaded when James loads the mailbox. The REST backend also has a comet function, so can push messages out to subscribers. How can I link this external message event with the internal James IMAP IDLE functionality?
Thanks, Martin On 7 January 2013 07:30, Eric Charles <[email protected]> wrote: > Hi Martin, > > The magic is in IdleProcessor [1] which registers a event listener and > produces unsolicited responses to the client further to events on the > mailbox. > > The mailbox project is responsible to generate those events. mailbox-store > does it for all the mailbox implementations, so you don't have to do > anything on you custom mailbox. mailbox-store will take care of idle for > you. > > Thx, Eric > > > [1] https://svn.apache.org/repos/**asf/james/protocols/trunk/** > imap/src/main/java/org/apache/**james/imap/processor/**IdleProcessor.java<https://svn.apache.org/repos/asf/james/protocols/trunk/imap/src/main/java/org/apache/james/imap/processor/IdleProcessor.java> > > > On 06/01/2013 12:20, Martin Hewitt wrote: > >> Hi all, >> >> I noticed that the CAPABILITY command issued to James includes the IDLE >> capability and was wondering how James accomplishes this? >> >> Is the logic in the MailboxManager somewhere or the Mail Store? How would >> I >> go about supporting this in a custom mailbox/mailstore environment? >> >> Thanks, >> >> Martin >> >> > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > server-user-unsubscribe@james.**apache.org<[email protected]> > For additional commands, e-mail: > [email protected].**org<[email protected]> > >
