The mapistore python layer does not handle PtypObject data type. We eventually have support for PT_OBJECT in exchange.idl but it sounds wrong to me was we handle it as uint32_t, hence no specific complex object type handling. Therefore I would say that is not only not handled properly in mapistore python REST API but also that OpenChange lacks support for this object type.
Are you aware of different use cases than PidTagAttachDataObject that would require to consider this PidTag more actively right now? For instance, we can open embedded messages from OpenChange without requiring to access this property afaik. On 14/09/15 17:22, Aleksander Machniak wrote: > This property is of type PtypObject. Is it supported in a way that does > not require building the binary blob, but use object/array instead? > > Specifically I'm talking about calendar event exceptions which are > supposed to be handled as attachments with PidTagAttachDataObject. > -- 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
