Hi Friends,
I have been working on stand alone application that reads application configuration from properties files.
I was thinking if it would be a better idea to store them in a table in the database.
This way, changes would be propagated faster
if we need to update a particular property, we don't necessarily have to go through the whole release cycle.
But this could be a disadvantage as well, as we are introducing un-tested features.
But these configuration changes do not happen often and if ever it happens we would actully know the risks.
What are your thoughts and experiences on this?
I would appreciate if someone throws some light on this.
Thanks,
Cnu
[EDIT] fixed subject to be more meaningful ( I think )
[ September 28, 2006: Message edited by: cnu sri ]
I have been working on stand alone application that reads application configuration from properties files.
I was thinking if it would be a better idea to store them in a table in the database.
This way, changes would be propagated faster
if we need to update a particular property, we don't necessarily have to go through the whole release cycle.
But this could be a disadvantage as well, as we are introducing un-tested features.
But these configuration changes do not happen often and if ever it happens we would actully know the risks.
What are your thoughts and experiences on this?
I would appreciate if someone throws some light on this.
Thanks,
Cnu
[EDIT] fixed subject to be more meaningful ( I think )
[ September 28, 2006: Message edited by: cnu sri ]