Re: Conf: argue !

> 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.

_a