Proposed Capabilities: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
=== Server as Client === | === Server as Client === | ||
Optionally servers will be able to act as an OPeNDAP client. This capability means that the server can read from other OPeNDAP data sources and use them as part of the server-side function calculation. This | Optionally servers will be able to act as an OPeNDAP client. This capability means that the server can read from other OPeNDAP data sources and use them as part of the server-side function calculation. This capability is implemented as part of [[|Current_Implementations#The_Ferret-Thredds_Data_Server_.28F-TDS.29|F-TDS]] and [[Current_Implementations#The_GrADS_Data_Server_.28GDS.29|GDS]] via a list of data sets in the first set of curly braces. | ||
=== Standard Functions === | |||
=== Native "scripts" === | |||
=== Security === | |||
Revision as of 19:30, 28 September 2007
Proposed Capabilities
We propose the following set of capabilities for servers that want to expose server-side functions to OPeNDAP clients. Clearly, some servers will go well beyond this and some of these requirements are identified as optional. One important requirement will be to implement the "getCapabilities" service so that clients can query the server about what it can do.
Capabilities Service
Servers will be able to respond with listing of functions and its capabilities as a client, and other information to be determined. How do we do this via OPeNDAP? Is is adequate for this to be
Server as Client
Optionally servers will be able to act as an OPeNDAP client. This capability means that the server can read from other OPeNDAP data sources and use them as part of the server-side function calculation. This capability is implemented as part of [[|Current_Implementations#The_Ferret-Thredds_Data_Server_.28F-TDS.29|F-TDS]] and GDS via a list of data sets in the first set of curly braces.
