On 04/20/2015 12:03 PM, Juan Valles wrote: > PtypBinary properties are always encoded in base64, yes (we detect > and encode them without caring about which particular property they are). I > agree that it is not optimal and your proposed solution looks good. However, > as we're not addressing optimisations yet, the status of this particular > code isn't likely to change in the short term.
A related question. Because fetching the body is an expensive operation and returning many attachments data in one request might simply exceed some memory/time limits on the server.... are attachment bodies expected to exist when listing attachments (e.g. GET /mails/(id)/attachments) or only in attachment info request (GET /attachments/(id)/)? Are there maybe "default sets of properties" for listing requests or sth? -- Aleksander Machniak Software Developer, Kolab Systems AG ------------------------------------------------------- PGP:19359DC1 - http://kolabsys.com - http://alec.pl _______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
