collection is specific to the REST API and rest.py. Its role is to define the name of the REST resource the message should be retrieved from. It is therefore independent from PidTagContainerClass as to speak because it reduces the choices to a strict and known set of REST collections. For example you can have different PidTagContainerClass values (IPM.*) that all represent calendar appointments or mail messages, or tasks. You can either have custom PidTagContainerClass value. You would therefore have to create a REST resource from every value which would be unmaintainable.
PidTagContentCount is a "meta" property which value is going to differ whether we want to retrieve regular messages or FAI messages on a folder. items_count therefore represent the overall number of messages in a folder, regardless of their nature and is a helper for rest.py to process folder's contents accordingly and compute a PidTagContentCount value. id and parent_id are defined and used to be compliant with the REST model where you need to have one unique resource per item but at the same time be able to navigate between parent/children. On 31/03/15 11:10, Aleksander Machniak wrote: > I see some inconsistency in folder properties naming. E.g. I see > "collection" and "items_count" in examples. There's also > PidTagDisplayName, so why not to use PidTagContainerClass and > PidTagContentCount? > > I also see "id" and "parent_id", but they do not exist in MS-OXCFOLD, so > I'm not complaining about these two. > -- Julien Kerihuel [email protected] 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 [email protected] http://mailman.openchange.org/listinfo/devel
