Re^6: Configuration Files

Actually, writing is not an issue, since the config is actually stored in a DB (albeit MySQL) until it's ready to be 'published'. And yes, the application itself runs on 7 servers. (Don't ask me why the DB only runs on one...).

All things being equal, I would use a DB and wouldn't even bother posting this here, but I've inherited an infrastructure that's not ideal (as is not likely to be changed much anytime soon), and also expectations on reliablilty inherited from the legacy application. I take your points though.

Comment on Re^6: Configuration Files

Replies are listed 'Best First'.
Re^7: Configuration Files by Anonymous Monk on Nov 03, 2004 at 12:08 UTC
I don't get it. How's that writing is not an issue, yet dragonchilds suggestion of reading it once isn't possible because the config file will be updated. What is it? In fact, the more I read, the more I get confused about your priorities. Reading in the config file needs to be efficient, yet the config file won't be updated often. It needs to be reliable and efficient, but a database can't be used. You're looking for alternatives, but it's unlikely your infrastructure will be changed. About any suggestion that's being offered is shot down because of "efficiency" or "reliability" reasons, or because of company politics. That doesn't give much leeway, does it?	[reply]

Replies are listed 'Best First'.

Re^7: Configuration Files
by Anonymous Monk on Nov 03, 2004 at 12:08 UTC

In fact, the more I read, the more I get confused about your priorities. Reading in the config file needs to be efficient, yet the config file won't be updated often. It needs to be reliable and efficient, but a database can't be used. You're looking for alternatives, but it's unlikely your infrastructure will be changed. About any suggestion that's being offered is shot down because of "efficiency" or "reliability" reasons, or because of company politics. That doesn't give much leeway, does it?

[reply]