On Fri, 2008-05-30 at 17:46 +1000, Brad Hards wrote: > Also, MAPI actually has two APIs with the same function name: > IMAPIFolder::SetReadFlags() - > http://msdn.microsoft.com/en-us/library/ms527975(EXCHG.10).aspx > which looks to be a wrapper for 0x66 > and > IMessage::SetReadFlags() - > http://msdn.microsoft.com/en-us/library/ms527993(EXCHG.10).aspx > which looks to be a wrapper for 0x11. > > So we also need to decide on API names for libmapi.
When we have potential name conflicts like this, we should avoid trying
to follow MSDN and implement the calls the way they appear on the wire.
So I'd propose the following naming:
- 0x66: SetReadFlags for IMAPIFolder::SetReadFlags()
- 0x11: SetMessageReadFlag for IMessage::SetReadFlags()
--
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
