At 10:26 AM 3/25/2007, Bernhard Hailer wrote: >I had such database corruption incidents several times already. >Same observation, it seems always to happen when transmitting. > >I actually would like to see some text based configuration file.
I can see some value in using XML.. it has a bit more structure than straight text (or, at least, it provides a syntax for tags.. rather than "roll your own"). It is hand editable. There are XML readers/writers available with useful APIs for most platforms. Some of the XML reader/writers are a bit of a resource pig, but in this application, I don't know that it would be crippling (presumably you're not hitting the configuration db on every dot and dash). I would imagine that you'd just load the whole thing into memory and deal with it there, so disk speed isn't a factor. I've gone back and forth on XML vs text for things like .ini files several times over the past few years for my own work. Either way works, and I've not found that the "work" involved in implementation is significantly different in the overall scheme of things. OTOH, PowerSDR is there, it works, it happens to use Access. You have the challenge of "do you modify the existing program to use something else" or "wait until PowerSDR 2.0 comes out and just live with the occasional hiccup". Not much has been said about how PowerSDR 2.0 will deal with these things, but given the (sometimes strident) calls for multiplatform support, it might happen without overt action. _______________________________________________ FlexRadio mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/ FlexRadio Homepage: http://www.flex-radio.com/ FlexRadio Knowledge Base: http://kb.flex-radio.com/
