You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<Description>Configuration Manager is an interface for managing configuration data.
32
35
User are expected to extend the core to provide concrete implementation for disk of database persistency.
33
36
34
-
This package contains a generic API for configuration data access. It includes a Collection class for multiple configurations and it includes a Cache class which provides in-memory configuration management.</Description>
37
+
This package contains a generic API for configuration data access. It includes a Collection class for multiple configurations and it includes a Cache class which provides in-memory configuration management.
38
+
39
+
*********
40
+
The ConfigurationManager project is aimed at providing the backbone for framework-agnostic configuration management. Developers can override data source, provide their own serialization/deserialization algorithms, encoding or encryption. It is meant to be used as an injectable configuration management tool where the developer chooses at runtime what is the configuration supported, thus allowing unit testing with dependency-injected configuration states, while accessing configuration from remote locations or local file in a production context.
41
+
42
+
This library proposes an abstract ConfigManager class and supplements it with a Cache ConfigManager (provides in-memory support) and a Collection ConfigManager (which aggregates an array of ConfigManagers). The CacheManager is a singleton in any given application instance (context). When merging managers into a Collection (or merging collections into a single one), the Cache managers are kept as a singleton. The Cache manager cannot be distributed over a network or shared in multiple application instances on the same machine. A distributed cache manager would be a specific type of manager that the developer can instantiate (it would act as a normal Config Manager).
43
+
44
+
Examples of Configuration Managers could be CfgManager.INI, CfgManager.mySQL, CfgManager.XML, etc.
45
+
46
+
During "Read" operations, the Collection of ConfigManagers is scanned until all elements have been found. If all elements are found in the first manager, it will not continue searching the other managers. Cache manager is always the last, unless the node specifies that it should be used preferably. On a successful read, the Cache manager is updated (Write) with the latest value.
47
+
48
+
During "Write" operations, the elements will be written in the first manager of the Collection, and Cache will be updated.</Description>
35
49
<Copyright/>
36
50
<Packager/>
37
51
<URL/>
38
-
<Release_Notes>Initial release - Configuration Manager with Collection and Cache support</Release_Notes>
52
+
<Release_Notes>Adding Variant Read and Write support (flattens/unflattens variants to/from Key Value Pairs)
53
+
This package now depends on LVOS DataManipulation package.</Release_Notes>
39
54
</Description>
40
55
<Destinations>
41
56
<Toolkit_VIs>
@@ -312,7 +327,35 @@ This package contains a generic API for configuration data access. It includes a
0 commit comments