On Wed, 2008-09-17 at 04:51 +0200, Julien Kerihuel wrote: > So far mapiproxy behavior works as expected and I can (or not) activate > the nspi server from smb.conf and reply to NspiBind queries properly. > I'll keep working on EMSABP server integration after some sleep and will > push a new status update this evening.
Hi List, I've been working on the NSPI server implementation, but I'm still a bit far from the implementation we want. In the same way that I added almost full Exchange schemas, I'm trying to implement emsabp so it the most complete as possible. If it was only about pushing existing emsabp code into mapiproxy, I could have done it within a day, but with the option I've chosen it will take more time and the server should (hopefully) be more robust, reliable and scalable. I've merging the code, but at the same time check in MS specs whether our NSPI server is compliant or not and fix the code in case we're doing something the wrong/incorrect way. Because 'take more time' is so vague, I'll push a preliminary emsabp update when I've finished to implement the full NspiGetSpecialTable and then update again each time there's a new improvement or change. I'll disable dcesrv_exchange.so compilation, but keep the code in trunk unless we have a feature-similar implementation in mapiproxy. Finally, I'll also push a skeleton for emsmdb and rfr server development in a separated commit soon. Conclusion, I didn't meet the deadline I had fixed but raised the stake during the development. I anyway keep focus on this task and will push updates when there is significant new results. Cheers, 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
