Hi List, We are about to merge the mapi_context branch back into trunk.
This branch was initially created to work on new libmapi semantics,
replacing the libmapi global context with a per-context implementation.
This work will improve OpenChange client framework on long-term and
offers a solid base for future libmapi python bindings development.
It also means that we have introduced some changes within the API that
will break existing applications and require updates. The only real
change is basically the usage of a mapi_context structure at
initialization, logon (create session) and uninitialization which will
get used as the root element in the memory allocation hierarchy.
It also gave us the opportunity to inspect our existing trunk and part
of the code are about to be removed:
- the torture suite: we don't use it anymore. It has been
replaced with our mapitest tool.
- Perl swig bindings: unmaintained for a while, we do prefer
focusing our time on the python bindings development.
- pymapi python bindings: This was the initial Jelmer's effort
for python bindings support. Most of the python bindings
development is done within pyopenchange and we plan on creating
the libmapi python bindings there.
Additional weeks may be required to stabilize the code and fix potential
memory leaks/inconsistencies introduced with the API change. We are
however convinced it is a worthwhile move for future developments.
If you are developing on top of OpenChange and encounter troubles using
the forthcoming API, do not hesitate to post on the list or get in touch
with us on IRC.
Kind Regards,
Julien
--
Julien Kerihuel
[email protected]
OpenChange Project Manager
GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
