439
edits
NSS Shared DB: Difference between revisions
Jump to navigation
Jump to search
→Layering
| Line 100: | Line 100: | ||
The database layer must be multi-thread safe. If the underlying database is not thread safe, sdb_ layer must implement the appropriate locking. | The database layer must be multi-thread safe. If the underlying database is not thread safe, sdb_ layer must implement the appropriate locking. | ||
===== sdb_FindObjectsInit ===== | |||
The database API consists of an initalization call, which returns an SDB data structure (defined below). | The database API consists of an initalization call, which returns an SDB data structure (defined below). | ||
| Line 119: | Line 121: | ||
* keydb is the returned key SDB structure | * keydb is the returned key SDB structure | ||
(NOTE: the signature of this fucntion is likely to change. <font color=red>Comments on how to change it would be appreciated</font>. Issues include: 1. Should cert and key versions be part of the API, or should they be part of the underlying database? 2. The cert and key prefix values are missing and should be added. 3. Do we need separate create flag or is the combined READ/WRITE/CREATE sufficient?). | (NOTE: the signature of this fucntion is likely to change. <font color=red>Comments on how to change it would be appreciated</font>. Issues include: 1. Should cert and key versions be part of the API, or should they be part of the underlying database? 2. The cert and key prefix values are missing and should be added. 3. Do we need separate create flag or is the combined READ/WRITE/CREATE sufficient? 4. need a way to supply the list of know attributes so old DB's can be updated and initialzied properly?). | ||
The returned SDB structure has the following format: | The returned SDB structure has the following format: | ||