Re: Conf: argue !

alex black schrieb:
>> The idea is simply that reading all confs from db can be very long, 
>> and it'sll be done from many parts of the code, for each page requested.
>> Whereas including a php file caching all confs is easy and probably 
>> fast. Db is useful to maintain the list of values and have a gui to 
>> edit them.
> 
> 
> Yes exactly -
> 
> you have a simple conf database which stored properties, take them out 
> of the DB and cache them.
> 
> great.
> 
>> Yes, build.properties. Or a reserved name and an xml conf: conf first 
>> reads conf/Conf.xml then is able to read conf from db.
> 
> 
> I wouldn't promote that all conf is exclusively in the DB - we need some 
> very basic system configuration (like database connection info) in files.
> 
> But everything else can go in a db.

This is why I proposed:

* Force the user to have a datasources.conf.xml XML configuration file 
for all datasources. They do not have to be edited at run time - they 
even cannot since you'd have to access the database you do not know 
about since it has not been configured.
* Force the user to have a binarycloud.conf.xml XML configuration file 
to have very basic settings like base_url etc. A page cannot be 
displayed without those settings anyway.

This solves the egg-chicken problem since you define two eggs from which 
all the other chickens can evolve.

Thoughts? Comments? Disagreements?


Manuel