Expanded arguments for Constraint Expressions: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(Created page with " << back {{subst:Project Description}}") |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Development#General_Development | << back]] | [[Development#General_Development | << back]] | ||
== Use Cases == | == Use Cases == | ||
# Pass in a Constraint Expression using POST | |||
# Pass in a CE using both POST and GET | |||
# Build an array as an argument for a server function | |||
== Definitions == | == 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 == | == Design == | ||
=== Constraints that are large === | |||
=== DAP Array arguments in CE functions === | |||
== Deliverables == | == 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 == | == Period of use == | ||
26 June 2013 onward | |||
Revision as of 20:34, 18 June 2013
Use Cases
- Pass in a Constraint Expression using POST
- 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
