On Fri, Jun 12, 1998 at 12:29:41PM -0400, Kevin Atkinson wrote: > [EMAIL PROTECTED] wrote: > > > > On Fri, Jun 12, 1998 at 12:23:28AM -0400, Kevin Atkinson wrote: > > > Second off > data will be regually exported to text based backup files (say like > every hour) so if something goes wrong it can easilly read the text > based file to fix the corrupted parts.
hmm this sounds good at first...but has some problems. First: What if the configuration error or orruption takes more than an hour (or even more than a day) before it is noticed? it could start dumping off corrupt data (depending on whether or not it notices the corruption) second: seems execcive > > > So what do you think of this idea? > > > > As you can see I don't like it. > > > > I could however see writing a library or some sort of "interface" that > > programs > > can use. This would take the burden of writting a parser and working out the > > more "exact details" of the configuration file off of the designer of the > > application, and place it on the library. > > > > This would allow the library to basically do whatyou say (make a database of > > I really just should not have mentioned the windows registry as most > people hate it. not most people....just those people who know of it and have had to deal with it :) > However what I was thinking off would is exactly what > you are thinking off. There will just be a server running where > programs can talk to to change their configuration. Thats not exactly what I was thinking of...I was thinking litterally of a library. just the code to do it in a nice dynamically linkable library. I don't see the need for a server running...those chores would best be handled by some other utility which uses the API. SUing an actual server for this seems like major overkill to me. > However it can also > translate things to in from the old fashion configuration files so that > applications don't have to use the library if they don't wants to. well thats the nice thing about the library...all you have to do is update the library, and use a utility to dump the old configs back through it... and presto...your using a new file format.. ALL programs which use the library would automatically use the new one. Ya know...while I think that the registry, database, and server are all overkill in their own way...I am almost surprized that such a library has never been written. I mean, think how many programs need to parse a config file? (btw HAS someone written such a library? if so I have never heard of it) -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]