S
scott_auge
Guest
Waaaay in the past, I have done this... Issue 3 uses a database table ( www.oehive.org/.../ezine3.pdf) . With all the remote access to databases expected these days, that is the best place to put it - otherwise you might need to move configs with movement of clients. Moving between environments (dev, test, prod) is merely moving the data. Issue 3 also gives lots of types of parameters that are stored too so take into consideration what gets stored. (Later on, I was storing HTML in configs as it was searched by {customer, app, parameter} so take that sort of thing in mind!) Issue 6 ( www.oehive.org/.../ezine6.pdf ) expands on Issue 3. The code for both is at www.oehive.org/.../ . It also includes code for making the files. I would use XML now days to store stuff. JSON might be "hot" but it is very web oriented. One can use it multiple interfaces (CHUI, GUI, WWW, Mobile) but storing things such as base64 and the like might be taken into consideration. XML is better for that.
Continue reading...
Continue reading...