1. you have your basic properties file. i.e. Something=Something else. You split off the first equals.
2. You have XML. We can argue that XML is hard to process or is easy to screw up, or not those cases. Not the point. It's viable and apache's httpd server uses it :)
c. You have ini files.
There are modules and really simple algorithms to implement any of these. Matter of complexity of your configuration ideas and how much you want users to tamper with them directly.
--
"So far my experience has been that most people who go for certification have broad but not deep knowledge in the field and the flavor of the knowledge is academic. But every once in a while one finds a gem of a person who learns all the time and uses certification to prove it." -- on Orkut
In reply to Re: Saving application configuration to files
by exussum0
in thread Saving application configuration to files
by crabbdean
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |