On 12/03/15 12:51, Aleksander Machniak wrote: > I just briefly reviewed the REST API documentation. > > 1. How do you ask for list of folders (top level in hierarchy)? I see > "GET /folders/(id)/folders" but no "GET /folders".... Oh, I found in the > python code that there is "GET /folders". Am I correct? Is it only > documentation issue? Indeed there is no GET /folders. By convention we have 2 reserved id per mailbox:
GET /folders/0/folders will retrieve the hierarchy of the NON IPM Subtree GET /folders/1/folders will retrieve the hierarchy of IPM Subtree (where Inbox, Calendar, etc. are) > > 2. I don't know MAPI nor Outlook, but I do know ActiveSync and as I know > non-email objects do not have attachments there. So, why there's e.g. > "GET /notes/(id)/attachments"? In MAPI, every message item can have attachments. For instance, you can add a picture to a contact or attach documents to a calendar entry. Outlook will perform a GetAttachmentTable on the message object if the PidTagHasAttach = true > > 3. I see /folders/*/fai in the code. It's also undocumented. I'm curious > if this is required and how much of objects-types of this kind there > will be needed. I mean, there's no such thing in the backend I'm working > with, so it would need to be handled somehow. FAI are folder associated information. These are messages that make no real sense for the mapistore REST backend but are required for Outlook to operate properly. It is therefore the reason why FAI have a dedicated resource name. In your case your backend does not handle them, you can simply store them as raw data and push them back to client, e.g. like mock backend. > > 4. What exactly I should/can return in /info? The documentation is indeed a bit lacking proper documentation. At this time, /info is used to list the contexts you backend provides, hence its capabilities. Basically, it is to know whether your backend wants to be Inbox, Calendar, Contacts, all of them or just one of them. In the case where you want a full replacement, you obviously want to replace them all. However it can be useful to combine this approach to the mock backend to focus on one item/root folder at the same time. What you need to return is therefore a list of contexts dictionaries, each entry with name, url, role and whether it is a main_folder or not. I will get back to you later today with a sample output of the rest backend in case you can't get it to work properly in the meanwhile. > > And one general question about folders hierarchy. In ActiveSync Outlook > does not support multi-folder e.g. in Calendar. Is it true for MAPI? > I.e. do I need to "flatten" the hierarchy into one folder per object type? In Outlook, you can have n calendars at the same level or a hierarchy of calendar objects if you want to. > ps. where can I find list of MAPI object properties (all or some minimal > set)? [MS-OXPROPS] from Microsoft Exchange protocols documentation is the right place to start. I would suggest you to download the full Exchange_Protocols.zip so you can navigate from one reference to the other and get further information on any of the properties you are searching: http://go.microsoft.com/fwlink/?LinkId=115073 -- 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
