Am Dienstag 22 Mai 2012, um 16:38:20 schrieb Christian Hilberg: > [...] > Seems the solution which is now in Git master solves only part > of what is needed (or I am missing something, in which case I > will happily accept correction). Okay, there's another bit missing in current CamelIMAPXServer for it to be generally usable inside CamelIMAPXStore derivatives. Extending the handler for untagged responses in CamelIMAPXServer is half of the deal. Having CamelIMAPXServer expose an API for sending custom IMAP commands from within a subclassed CamelIMAPXStore is the other. In the older evolution-kolab code I've changed CamelIMAXServer to expose imapx_server_command_run_sync(), which was enough for me to send my custom annotation CamelIMAPXCommands for querying and setting IMAP folder annotations. However, this may not be The Right Thing(TM) to do, telling from the code comments in imapx_server_command_run_sync(). We may need to be able to queue CamelIMAPXJobs and wait for their completion. The imapx_server_command_run_sync() approach was simple and sufficient for my few annotation commands, but it may not be good enough for general use. Chen, you know IMAPX a whole lot better than I do, so I'll ask you to expose the right functions for sending custom IMAP commands. Kind regards, Christian -- kernel concepts GmbH Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/
Attachment:
signature.asc
Description: This is a digitally signed message part.