OC Library Features and Analysis: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary
Line 1: Line 1:
== Features ==
== Features ==
''Features likely needed by any general C-language client-side API for DAP''
''Features likely needed by any general C-language client-side API for DAP''
# DAP 3.x protocol version negotiation
=== features already implemented in oc ===


# get variables (primitive types)
# get variables (primitive types)
# get array varaibles (of primitive types)
# get array varaibles (of primitive types)
# get structures (flat and nested)
# get sequences (flat and nested)
# get grids
# get arrays of constructor types
# get attributes
# get attributes
=== features that can be implemented with little effort ===
''little means using the current library's structure and some more code''
# make print representations for all responses (DAS, DDS, DataDDS)
# make print representations for all responses (DAS, DDS, DataDDS)
# allow constraints
# http authentication support
# http authentication support
# SSL suport
# SSL suport
Line 17: Line 20:
# compression support
# compression support
# testing - write automated tests
# testing - write automated tests
# parse XML(DDX, DataDDX*)
# shared dimensions*
# groups*
# DAP 3.x protocol version negotiation
# more typical API (open, read, close all based on an opaque parameter - object - and C's existing data types)
# nightly builds
# nightly builds
# automated build (autoconf, make, libtool)
# automated build (autoconf, make, libtool)
# more typical API (open, read, close all based on an opaque parameter - object - and C's existing data types)


=== features already implemented in oc ===
=== features that will be hard to implement ===
''hard means extending the existing library's structure/implementation''


=== features that can be implemented with little effort ===
# get structures (flat and nested)
 
# get sequences (flat and nested)
=== features that will be hard to implement ===
# get grids
# get arrays of constructor types
# parse XML(DDX, DataDDX*)
# shared dimensions*
# groups*
# allow constraints for the DDS
# allow constraints for the DataDDS (e.g., lat or lon or '''lat and lon togther''')


== Use Cases ==
== Use Cases ==

Revision as of 23:33, 14 January 2009

Features

Features likely needed by any general C-language client-side API for DAP

  1. DAP 3.x protocol version negotiation

features already implemented in oc

  1. get variables (primitive types)
  2. get array varaibles (of primitive types)
  3. get attributes

features that can be implemented with little effort

little means using the current library's structure and some more code

  1. make print representations for all responses (DAS, DDS, DataDDS)
  2. http authentication support
  3. SSL suport
  4. cookie support
  5. .dodsrc support (read and write)
  6. compression support
  7. testing - write automated tests
  8. nightly builds
  9. automated build (autoconf, make, libtool)
  10. more typical API (open, read, close all based on an opaque parameter - object - and C's existing data types)

features that will be hard to implement

hard means extending the existing library's structure/implementation

  1. get structures (flat and nested)
  2. get sequences (flat and nested)
  3. get grids
  4. get arrays of constructor types
  5. parse XML(DDX, DataDDX*)
  6. shared dimensions*
  7. groups*
  8. allow constraints for the DDS
  9. allow constraints for the DataDDS (e.g., lat or lon or lat and lon togther)

Use Cases

Definitions

Background

Deliverables

Period of use

Retrieved from "https://docs.opendap.org/index.php?title=OC_Library_Features_and_Analysis&oldid=2806"