Brent Sarten wrote:
Will do. I'm unclear as to the goal of this portion of the project, though. As I understand it, the goal is to provide an API that exposes all the groupware functionality of Exchange, and the MAPI SP bit just exposes things that are already available...through MAPI. Is that a fair analysis?
You're right, it's not compulsary. I did the message store so that OpenConnector would solve the dependence on PST file format had hence allow easy access to third party tools, and also to minimize our dependence on MS message store quirks.
Also, initially the goal was to allow developers with ideas for unique message store backends to implement those easily by a drop in backend plugin system. We removed the drop-in plugins, but those backends can still be done by remimplementing IMAPIProp and probably one or two other interfaces.
- Kervin
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ otlkcon-devel mailing list otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
