|
|
Library Description Errors | Parameters Return Value See Also |
SYNOPSIS
# include <cdsa/mds.h>
CSSM_RETURN CSSMAPI MDS_Initialize(const CSSM_GUID *pCallerGuid,const CSSM_DATA *pCallerManifest,const CSSM_MEMORY_FUNCS *pMemoryFunctions,MDS_FUNCS_PTR pDlFunctions,MDS_HANDLE *hMds)
cdsa$mds300_shr.exe
)pCallerGuid (input/optional) | ||
The GUID of the module calling MDS. | ||
pCallerManifest (input/optional) | ||
The Manifest of the module calling MDS. | ||
pMemoryFunctions (input) | ||
The memory-management routines MDS uses to allocatequery results on behalf of the caller. | ||
pDlFunctions (output) | ||
The function table containing MDS programming interfacesfor database access. | ||
hMds (output) | ||
A new handle that can be used to interact with theMDS. The value will be set to CSSM_INVALID_HANDLE if the functionfails. |
If the caller is a CDSA service provider that will requirewrite-access to an MDS database, (such as a module that supportsdynamic insertion and removal events), then the caller can providethe caller's GUID as input parameter pCallerGuid
.When provided as input, the GUID is associated with the MDS handleand is used during DbOpen
processing. If write-accessis requested during DbOpen
, MDS uses the associatedGUID to locate the service provider's signed manifest credentialsin the DS Common
relation. The service provider moduleand its credentials are verified to ensure that write-access ispermitted on this database by this module.
The installers will have to provide the pCallerManifest
insteadof pCallerGuid
, as GUID cannot be used to locatean application unless it is installed. Only one of the two parameters pCallerGuid
and pCallerManifest
shouldbe non NULL in an MDS_Initialize()
call, otherwise an error will be returned.
CSSMERR_DL_INVALID_POINTERCSSMERR_DL_INTERNAL_ERRORCSSMERR_DL_MEMORY_ERRORCSSMERR_DL_FUNCTION_FAILED
Intel CDSA Application Developer's Guide
|
|