OPeNDAP Server Development

1
OPeNDAP Server Development

• James Gallagher
• 15 May 2006

2
Server4

• DDX
• THREDDS
• SOAP

3
DDX

• DAS DDS --gt XML --gt DDX
• One response/object holds all metadata
• Similar to CDL file
• Fix servers attribute structure
• XML chosen to
• Ease the parser problem
• Facilitate SOAP

4
THREDDS

• Used to replace HTML-only directory
• XML provided for programs HTML version for
  browser rendering
• Emerging standard already supported by some other
  DAP-compliant servers
• Server will support customized directory views

5
SOAP

• Interface supports bundling several requests in
  one message THREDDS and DDX/DataDDX in one
  message. This combines directory, inventory and
  data in one message
• Although not implemented, the interface can
  support asynchronous interactions.
• Interface supported by some commercial software
• But they will still need our code to read the
  responses
• Easy to support GET/REST and SOAP