OC Library Features and Analysis: Difference between revisions
Line 12: | Line 12: | ||
What is the DRNO API in which you refer to in your html documentation? | What is the DRNO API in which you refer to in your html documentation? | ||
How do the walkmap and walkdata functions work? How does "active" work with regards to these functions? | |||
When is ocdump.c being used (dumpnode in particular)? | |||
== Features == | == Features == |
Revision as of 16:43, 27 January 2009
Questions
How do you build the Getdata* structure? That is, when you call makegetdata(), how do you build the OCnode* target structure?
How do the startp, countp, stridep parameters fit into the overall pattern of DAP's constraint expressions? For example, lots of DAP things are not arrays.
Why does the oc code parse the constraint expression since the server is the place where it's actually evaluated?
Once you get a Getdata* structure, how do you get the data out?
Suggestion: Change the name of the oc internal structure/type Sequence to a name not used by DAP.
What is the DRNO API in which you refer to in your html documentation?
How do the walkmap and walkdata functions work? How does "active" work with regards to these functions?
When is ocdump.c being used (dumpnode in particular)?
Features
Features likely needed by any general C-language client-side API for DAP
features already implemented in oc
- get variables (primitive types)
- get array varaibles (of primitive types)
- 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)
- http authentication support
- SSL suport
- cookie support
- .dodsrc support (read and write)
- compression support
- testing - write automated tests
- nightly builds
- 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 that will be hard to implement
hard means extending the existing library's structure/implementation
- get structures (flat and nested)
- get sequences (flat and nested)
- get grids
- get arrays of Structure
- 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)
- DAP 3.x protocol version negotiation