... new¹

Even though the UNIX/Internet combination has existed for more than 10 years, it is only recently that systems like the WWW have seen widespread use. Previously data was shared over the Internet using ftp or similar systems.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... implementation²

In order to use a given data display or analysis program with DODS, users or system managers must re-link those programs with the DODS reimplementations of the APIs used by those programs. DODS currently supports two APIs: netCDF and JGOFS. Support is planed for HDF and the formats GRIB and BUFR.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... information³

The text is a mini-DDS which can be parsed and instantiated using the DODS tool kit software.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... API⁴

It is possible that a user program might perform an operation such as looking in one data base for a file name and then opening the named file--this doesn't count as a manipulation of the file name.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... built⁵

In practice data servers for the supported APIs and several data formats will be available with the DODS software distribution.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... independently⁶

Some optimizations may introduce limited dependence via a data cache.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... DAS⁷

Structure charts are used to describe the design of the data server programs rather than object diagrams because these components depend, to a large extent, on the functional APIs used to access the data sets.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... server⁸

Which is actually a collection of three largely independent programs.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... close⁹

Because the DAP is a read-only protocol, we are not concerned with any operations that write data.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.