Exchange 2010 APIs
Exchange’s history with APIs is checkered at best and poor at worst. APIs have appeared in one release and disappeared in the next, and developers have been unable to depend on an API lasting more than a couple of releases, which is not a good basis on which to plan for a project that wishes to leverage Exchange data. MAPI is the ever-present API in both server and client versions, but it’s a difficult API to master as the documentation is sparse and most of the expertise exists within Microsoft. Other APIs such as Web Distributed Authoring and Versioning (WebDAV) were hailed with great anticipation as the “next great thing” when they appeared and have slowly decreased in importance, and others such as Exchange Routing Objects ...
Get Microsoft® Exchange Server 2010 Inside Out now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
