ServerDispatchOperations: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Line 6: Line 6:
=URL Dispatch Operations=
=URL Dispatch Operations=


Dispatch is the process in which an OPeNDAP server receives and interprets a request that comes in the form of a URL.
Dispatch is the process in which an OPeNDAP server receives and interprets a request that comes in the form of a URL. OPeNDAP servers can provide number of services and response for information. Some of these response will be clearly defined DAP2 responses, while others may be less rigidly designed.
 
==Special Requests==
 
Hyrax and other servers may support some special requests. These may be a secure server administration interface, help information, server status, or system properties. There is no clearly defined set of special responses, and their implementation is left up to the various server developers.
 
Hyrax currently supports:
 
* help - The URL http://your.host:port/opendap/help will take you to an help web page.
 
==DAP2 Responses==
 
 
 
==Version Response==
 
==File Access Responses==
 
==THREDDS Responses==


=Errors=
=Errors=

Revision as of 11:51, 6 February 2008

Now that Hyrax has been released it has become clear that we need to publish a paper that describes the correct behavior of an OPENDAP server. This should include the details of:

  • Dispatch - How the various request URL's get assessed and which responses are sent.
  • Errors - Which errors should be associated with which dispatch paths.

URL Dispatch Operations

Dispatch is the process in which an OPeNDAP server receives and interprets a request that comes in the form of a URL. OPeNDAP servers can provide number of services and response for information. Some of these response will be clearly defined DAP2 responses, while others may be less rigidly designed.

Special Requests

Hyrax and other servers may support some special requests. These may be a secure server administration interface, help information, server status, or system properties. There is no clearly defined set of special responses, and their implementation is left up to the various server developers.

Hyrax currently supports:

DAP2 Responses

Version Response

File Access Responses

THREDDS Responses

Errors

SOAP Dispatch Operation