Customer notices a behaviour in Alfresco IMAP that is not seen with the other IMAP server they use:
when a content is added to Share in may take a much longer time for the client to notify the IMAP client that the new content has been added.
1) Comparing our CAPABILITY line with e.g. Dovecot's
I see that we are missing the IDLE feature.
IDLE has been created for exactly the purpose of notifying the client.
2) more information on IDLE:
a) RFC 2177: IMAP4 IDLE
(lists also the client that support it. The list inclused Outlook and Thunderbird)
3) see also the concept of PUSH in IMAP:
"IMAP4 clients need to maintain a TCP/IP connection to the IMAP server in order to be notified of the arrival of new mail. Notification of mail arrival is done through in-band signaling, which contributes to the complexity of client-side IMAP protocol handling somewhat. A private proposal, push IMAP, would extend IMAP to implement push e-mail by sending the entire message instead of just a notification. "
(creative commons article attached)
4) Note that this is still a client-server model, and not a bidirectional link like websockets for instance.
5) Note that without IDLE you could still request for the changes but that's heavier and we need to understand how many clients one server can handle. Each client can set a frequency of poll, for Outlook 2011 and 2013 see e.g
6) To give a visual impression of how comfortable an immediate apparition is I attached videos about the Alfresco imap delays:
and the Dovecot immediate apparition:
as well as dovecot dump filedump_dovecot_idle.pcap
that shows that connections with IDLE are just 'held' until something new appears.