Hi there, reading about the new IMAPX implementation used by Evo >=2.30, I found it stated that "Maybe if imapx had come up before, many backends such as groupwise, mapi etc. would have followed this design rather than a sync one." -- Chenthill in [1] Does this mean that the Camel IMAPX code is ready to support a backend like ours (for Kolab2) to be implemented as an async one rather than a sync one (which is the case for the MAPI-, Exchange- and SCALIX-Backends (and maybe others, too))? Best regards, Christian [1] http://chenthill.wordpress.com/2010/01/11/evolution-with-improved-imap-support-imapx/ -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 Fax: +49-271-771091-19 D-57072 Siegen http://www.kernelconcepts.de/
Attachment:
signature.asc
Description: This is a digitally signed message part.