ConfDraft

http://www.binarycloud.com/index.php/Drafts/NewConfigurationDraft

Agree with everything up to "Architectural Redesign":

I dislike the name "ConfServer" because Server implies a daemon of some
sort. I would prefer ConfContainer or other such "storage" language. I'll
make a specific suggestion later when I am not in a rush :)

Under "The database schema"

I disagree with the schema, as I don't like the /1 /0 thing for arrays. See:

http://lists.binarycloud.com/pipermail/dev/2005-February/000023.html

for my comments on this subject.


I see some things missing:
-conf "levels" like default, etc. and the logic to assemble them from the
database so they override properly.
-no fields in the table to handle target levels (like dev, dist)
-no fields to handle language overrides (which are handled in the XML file
naming for XML?)
-how string replacement in conf values will be handled
-how CONSTANTS will be handled
-how problems with 'setting' into a database will be handled
-manuel(?)'s concept of immutable values (in my mind VERY important)

I would like to see comment but not necessarily action recommended by the
draft how Conf might in the future be used to handle "user preferences"
since we did discuss that earlier.

good work all,

:)

_a
_______________________________________________
dev mailing list
dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected]
http://lists.binarycloud.com/mailman/listinfo/dev