Expanded arguments for Constraint Expressions: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary |
|||
Line 2: | Line 2: | ||
== Use Cases == | == Use Cases == | ||
==== Pass in a Constraint Expression (CE) using POST ==== | |||
# Pass in a CE using both POST and GET | #The DAP client builds a CE using the existing syntax as a UTF-8 string | ||
#The client binds the POST information (request document body) to the URL and dereferences the URL | |||
#The server detects an inbound request using POST | |||
#The server rejects the POST request if the size of the request document body is larger then some upper limit set in a configuration file, returning an HTTP error code to the client | |||
#The server processes the request and returns a response | |||
#The client reads the response | |||
==== Pass in a CE using both POST and GET ==== | |||
==== Build an array as an argument for a server function ==== | |||
== Definitions == | == Definitions == |
Revision as of 20:47, 18 June 2013
Use Cases
Pass in a Constraint Expression (CE) using POST
- The DAP client builds a CE using the existing syntax as a UTF-8 string
- The client binds the POST information (request document body) to the URL and dereferences the URL
- The server detects an inbound request using POST
- The server rejects the POST request if the size of the request document body is larger then some upper limit set in a configuration file, returning an HTTP error code to the client
- The server processes the request and returns a response
- The client reads the response
Pass in a CE using both POST and GET
Build an array as an argument for a server function
Definitions
Background
This should be completed before 26 June 2013.
The MIIC project would like to be able to pass modest sized arguments into server functions they have defined. The arrays should be passed into the functions as single BaseType Array objects, not as collections of 100s ++ of BaseType objects.
Design
Constraints that are large
DAP Array arguments in CE functions
Deliverables
A new version of Hyrax on the trunk such that a special branch can be formed for the MIIC project to use. Once the feature is stable, make a Hyrax 1.9 branch which should include this feature.
Period of use
26 June 2013 onward