On 06/17/2015 03:47 PM, Julien Kerihuel wrote: > This attachment push mechanism is implemented in the save() operation > and we could reuse it, but I think a small variation may be required. I > would eventually propose - need further iterations/discussion - > something like: > > 1. GET /mails/submit > retrieve a submission context id (temporary), here id > 2. POST /mails/(id)/attachments > push attachments and associate them to this temporary context
That would work, but... On backend side we'd still need to store the mail properties and attachments somewhere, and it would be probably a message in Drafts folder (or special Configuration folder). So, in such a case I don't see a need for special actions like above. We could do: 1. POST /mails - to create a mail draft 2. Use existing /attachments actions to add/remove/edit attachments of the draft, and then > 3. POST mails/(id)/submit > push the contents of the email I only don't know how it fits with standard Outlook drafts handling. >From what you've said I understand that Openchange does not push every MessageObject operations to the backend, I have no idea how Outlook works, but maybe it should be changed in a way that when Outlook starts to "compose" a message Openchange creates a draft message on the backend and then updates it successively. -- Aleksander Machniak Software Developer Kolab Systems AG: http://kolabsys.com PGP: 19359DC1 _______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
