Hi Christian,
Libmapistore is indeed the point of entry for any backend to OpenChange server. For the past 2 years, we have developed a backend for SOGo, that is fairly usable and is gaining in maturity, besides a few undocumented issues that are still being sorted out.
As the developer of that backend and of the mapistore backend code, I would suggest you to use the sogo branch of the openchange repository, as this is the most debugged and advanced branch with regards to the server API.
You might also want to download SOGo 2.0, which includes the code for the SOGo OpenChange backend (subdirectory "OpenChange/") and which I think could be a good starting point. Of course, it is specific to SOGo, but the interface code can be used to understand further how this all work together.
I know Julien Kerihuel has written some documentation about the backend API. It may be slightly incomplete but should be quite up-to-date. I would also recommend the following documentation from Microsoft on the Exchange protocols: oxprops, oxcrops, oxcmsg, oxcfold, oxosfld, oxocal, oxocntc, oxomsg. Those are the references that are used the most in a backend, since they contain the description of the properties and the structures in use by the objects in a groupware such as Kolab or SOGo.
Otherwise, you can feel free to ask me questions if you want and I'll be glad to help as time permits.
Wolfgang _______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
