From bd327ff2bc0ae0922c063f0d40342669e7d6d7b3 Mon Sep 17 00:00:00 2001 From: Will Budic Date: Fri, 28 Feb 2020 20:55:35 +1100 Subject: [PATCH] Propery names are variables programatically. --- CNF_Specs.md | 32 ++++++++++++++++++++------------ 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/CNF_Specs.md b/CNF_Specs.md index 8fdb8d6..d86aa10 100644 --- a/CNF_Specs.md +++ b/CNF_Specs.md @@ -36,28 +36,36 @@ Which is pretty much welcomed and encouraged. 10. Constants are usually scripted at the beginning of the file, or parsed first in a separate file. 11. The instruction processor can use them if signifier $ surrounds the constant name. Therefore, replacing it with the constants value if further found in the file. - ```HTML +```HTML <<>> <>> ``` -12. CNF Constant values are store specific. -13. Constants can't be changed for the life of the application or service issued. -14. Storage of CNF constants can be preceded to the file based one. -15. i.e. If stored in a database or on a network node. After the file declaration fact. -16. Missing file based storage setting can be next queried from the environmental one. -17. This is to be avoided if possible. +12. Property names, Constant, Anon refer to the programmatically assinged variable name. +13. CNF Constant values are store specific. +14. Constants can't be changed for the life of the application or service issued. +15. Storage of CNF constants declared can be preceded to the file based one. +16. i.e. If stored in a database or on a network node. After the file declaration fact. +17. Missing file based storage settings can be next queried from the environmental one. + 1. This is to be avoided if possible. 18. File storage encountered constants override system environmental ones. 1. i.e. System administrator has set them. 19. Database storage encountered constants override file set ones. 1. i.e. User of application has set them. 20. CNF Constant values can be changed in the script file. - 1. If not present in script file, then an application setting must procede with its default. - 2. CNF Constants can be declared only once during parsing of script files. - 3. CNF Anons can overide in contrast previously assigned value. + 1. If not present in script file, then an application setting must procede with its default. + 2. CNF Constants can be declared only once during initial parsing of script files. + 3. Rule of thumb is that Constants are synchonized with an applications release version. + 4. Static constants, are script or code only assigned values. + 5. CNF Anons can overide in contrast previously assigned value. 21. A CNF Anon is similar to constants but a more simpler property and value only pair. - 1. Anons are so called because they are unknown or unexpected by the configuration framework. - 2. Also constants that turn up in the anon list, are a good indicator that they are not handled from script. Forgotten become anons. + 1. Anons are so called because they are unknown or unexpected by the configuration framework, store to object intermidiate. + 2. Constants that turn up in the anon list, are a good indicator that they are not handled from script. Forgotten become anons. + 3. Anons similar to constants, once in the database, overtake the scripted or application default settings value. + 4. Static anons, are those that are set in the database, and/or are not merged with application defaults. + 5. Anons hashed are programatically accessed separately to constants. + 1. It is fine to have several different applications, to share same storage, even if they have different implementation. + 2. Contants will be specific to application, while anons can change in different purpose script files. 22. Anon is not instruction processed. Hence anonymous in nature for its value. 23. Anon has no signifier, and doesn't need to have an application default. 24. Anon value is global to the application and its value can be modified. -- 2.34.1