|
There are quite a few "good" answers to your question, but each
answer needs to be weighed in light of your needs.
There are pro's and con's to using DNS for storage, so first you
need to define what your goals are in regards to the data you want
to store. AFter you have defined the constraints of the problem
we can better help you in determing what your needs are.
Some questions that need to be reviewed/answered are:
- the scope of availability of the data
(per user, per system, per network)
- the data life span
(short or long term; such as: computational data used in
anaylizing something would in many cases be short term, while things
like reference data is long term)
- usage of the data
(do you want to be able to historically record the information?)
- access time
(DNS has overhead, can you processing/use of the data absorb
this)
Right now I don't have time to get into the ifs and whys of private
versus public storage, so if some one else does, please do. Otherwise
I will see what I can do about putting something in later.
jill
|
| HI, -Just my opinion
Please only use DECdns for "global" information that will be accessed
by a large number of applications/users/... And put in as little
information as possible.
And as you said (re .0), use DECdns as a pointer to a system where
the detailed information resides.
---DECdns is a global naming service and NOT a distributed database---
===Steve
|