I think that "Virtual DNS" is a great feature of 4DIAC. However, I feel that its name simply does not fit.
Of course, it is very useful in mapping symbolic names to IP addresses. But even there, it more closely resembles a good old HOSTS file than DNS with all its servers and, well, domains. And nothing is being virtualized at all.
In the end, "Virtual DNS" simply maps (string) keys to (string) values. It provides a convenient way to define symbolic constants - or named constants -, not variables, as it currently says in the editor, since variable values would change during runtime.
So, that's the first thing I would change: Replace the column heading "Variable" in the Virtual DNS editor with "Name".
And, following this up: Why not simply call the whole thing "Named Values"?
Other names that I came up with: App Constants, ValueMap, Dictionary. But I like "Named Values" best and make it my suggestion.
Are there related considerations that I have missed?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think that "Virtual DNS" is a great feature of 4DIAC. However, I feel that its name simply does not fit.
Of course, it is very useful in mapping symbolic names to IP addresses. But even there, it more closely resembles a good old HOSTS file than DNS with all its servers and, well, domains. And nothing is being virtualized at all.
In the end, "Virtual DNS" simply maps (string) keys to (string) values. It provides a convenient way to define symbolic constants - or named constants -, not variables, as it currently says in the editor, since variable values would change during runtime.
So, that's the first thing I would change: Replace the column heading "Variable" in the Virtual DNS editor with "Name".
And, following this up: Why not simply call the whole thing "Named Values"?
Other names that I came up with: App Constants, ValueMap, Dictionary. But I like "Named Values" best and make it my suggestion.
Are there related considerations that I have missed?