NSTServiceEntry
NSTServiceEntry |
Message service entry point function for a MAPI store provider to wrap a PST-based local store as an NST store.
Quick Info
Implemented by: | MAPI provider |
Called by: | MAPI |
|
Parameters
NSTServiceEntry uses the MSGSERVICEENTRY function prototype. For information on its parameters, see MSGSERVICEENTRY.
Return Values
For information on return values, see MSGSERVICEENTRY.
Remarks
When using GetProcAddress to look for the address of this function in msmapi32.dll, specify "NSTServiceEntry" as the procedure name.
To use the Replication API, a MAPI store provider must first open and wrap a PST-based local store by calling NSTServiceEntry. The provider can then use the major interfaces of the API, IOSTX and IPSTX, to carry out replication.
The following remarks apply to an NST store:
- Do not store any information in the global profile section when implementing a MAPI provider that uses NSTServiceEntry. The global profile section is shared by many providers and data stored in this profile can be overwritten.
- Only items with existing modification time stamps get their stamps updated when they are saved.
- Conflict-checking does not occur automatically when items are saved.
- Duplicate detection does not occur when items are saved.
- The file representing the cached version of the server is appended with .NST.
- To obtain a pointer to the global profile section, a message service calls IMAPISupport::OpenProfileSection in the support object using pbNSTGlobalProfileSectionGuid as defined below:
#define pbNSTGlobalProfileSectionGuid "\x85\xED\x14\x23\x9D\xF7\x42\x66\x8B\xF2\xFB\xD4\xA5\x21\x29\x41"
See Also