It sounds like just the thing I want for tracking configuration information
similar to what’s found in an INI file, except that it doesn’t seem to have
any file reading or storing capabilities.
“Chris Rose” <chris.rose@viasat.com> wrote in message
news:a83c0l$3gq$1@inn.qnx.com…
It sounds like just the thing I want for tracking configuration
information
similar to what’s found in an INI file, except that it doesn’t seem to
have
any file reading or storing capabilities.
The ds (data server) daemon does almost nothing. It simply allows you to
associated a tag with a data value (indeed much like an INI file), however,
it is strictly memory based repository. It can also trigger an event when
the data associated with a tag changes. It’s main purpose in life is to
create an easy interface to dynamic HTML, although it would also serve the
purpose of a memory based configuration repository quite well also. You
would simply need to store all the data in one big INI file, and write a 10
liner that read the INI file and posted the data into ds (through the
ds_set() call). If each of your applications created the tags (they
should - after all know what config data they are interested in), and
registered an event with each tag, then they would all be asynchronously
notified to read the values for their tags when the “10 liner” wrote the INI
data into the server.
Rennie