- Different Types of Configuration Data
- Dealing with Configuration Data in VB6
- The Design Perspective
- Centralization
- Persistent Storage
- Access Mechanism (and Transient Storage)
- Summary of Persistent Storage and Access Mechanisms
- How and When to Refresh the Cached Configuration Data
Summary of Persistent Storage and Access Mechanisms
Not all access mechanisms can be used with all persistent storage mechanisms. Table 1 presents the possible combinations.
Table 1 Possible Combinations of Access Mechanisms and Persistent Storage Mechanisms
|
SPM |
OC |
Shared Member |
Thread Static |
OP |
Database server |
OK |
N/A |
OK |
OK |
OK |
Registry |
OK |
N/A |
OK |
OK |
OK |
Active Directory |
OK |
N/A |
OK |
OK |
OK |
OC |
OK |
OK |
OK |
OK |
OK |
.config file |
OK |
N/A |
OK |
OK |
OK |
As you see in Table 1, only OC is a bit inflexible as an access mechanism because it is so closely related to its storage. You can let the users affect OC as an access mechanism by using the Admin API for COM+ to change the stored value, but it is sort of a hack. At least, I don't think this was the way OC was supposed to be used.