Implementing a Logon Object

Every address book, message store, and transport provider instantiates a logon object as part of its implementation of IABProvider::Logon, IMSProvider::Logon, or IXPProvider::TransportLogon. Logon objects implement methods that help MAPI service client requests. Depending on your type of service provider, your logon object will support the following interface.

Address book and message store providers implement these features in their logon objects:

• Support for event notification (Advise and Unadvise methods). For an overview of event notification, see Event Notification in MAPI. For information about supporting notification in your logon object, see Supporting Event Notification.
• Entry identifier comparison (CompareEntryIDs method). For general information about entry identifiers, see Entry Identifiers. For information about comparing entry identifiers in your logon object's CompareEntryIDs method, see Supporting Object Access and Comparison.
• Access to additional error information (GetLastError method). For more information about handling errors in MAPI, see Error Handling.
• Access to objects implemented by the service provider (OpenEntry method). For more information, see Supporting Object Access and Comparison.
• Access to a status object (OpenStatusEntry method). For general information about status objects, see Status Objects. For specific information about implementing a status object, see Implementing a Status Object.
• Logoff (Logoff method). For more information, see Shutting Down a Service Provider.

If your provider is an address book provider, you will also implement these methods and associated features:

• GetOneOffTable to provide a listing of the templates that you support for creating new recipients. For more information, see One Off Tables or Implementing a Provider One Off Table.
• OpenTemplateID to provide access to the implementation of a recipient whose data resides in a host address book provider. For more information, see Acting as a Foreign Address Book Provider.
• PrepareRecips to insure that the appropriate properties are available for all of the recipients in a recipient list. For more information, see IABLogon::PrepareRecips.

A transport provider's logon object, which implements IXPLogon, is quite different from the logon objects implemented by the other types of service providers. It has only two features in common with the other logon objects: access to a status object through the OpenStatusEntry method and a logoff operation through the TransportLogoff method. Transport providers implement the following unique features in their logon objects:

• Registration for address types (AddressTypes method) and message options (RegisterOptions method). For more information about registering an address type, see Creating a Minimal Transport Provider or Transport Provider-MAPI Spooler Operational Model. For more information about registering message options, see Implementing Message and Recipient Options with Transport Providers.
• Control of message transmission (StartMessage, EndMessage and SubmitMessage methods). For more information, see Message Reception Model, Interacting with the MAPI Spooler, and Message Submission Model.
• Internal state validation (ValidateState method).
• Ability to download or upload messages on demand (FlushQueues method). For more information, see Implementing the FlushQueues Method.
• Ability to query for pending messages (Poll method). For more information, see Message Reception Model.
• Idle state detection (Idle method).
• Interaction with the MAPI spooler (TransportNotify method).