On 25/05/15 09:06, Aleksander Machniak wrote: > 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? >
At the moment, the body is fetched along with other properties and cached on the server. The semantics of the attachment API is indeed still pretty trivial in rest.py. The objective with next iteration is to fetch attachment body as a streaming object and have the offset matching the bottom-up from MAPI request to backend data. -- Julien Kerihuel j.kerih...@openchange.org OpenChange Project Founder Twitter: http://twitter.com/jkerihuel GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
