Server-side Functions: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(New page: == Server-side Functions Working Group == === Motivation === May different OPeNDAP server implementations include the ability to request that the server process the data before returning t...)
 
No edit summary
Line 10: Line 10:
=== Members ===
=== Members ===
# [mailto:Roland.Schweitzer@noaa.gov Roland Schweitzer]
# [mailto:Roland.Schweitzer@noaa.gov Roland Schweitzer]
# [mailto:pwest@ucar.edu Patrick West]


=== Resources ===
=== Resources ===

Revision as of 00:55, 25 September 2007

Server-side Functions Working Group

Motivation

May different OPeNDAP server implementations include the ability to request that the server process the data before returning the data to the requesting client. In some implementations, the client requests the processing by embedding the instructions into the URL of the request (GDS, F-TDS) . Other implementations favor putting the processing request into the query string of the URL(pyDAP, I think).

This working group will explorer the feasibility of developing a single method and syntax to request server-processing for common types of transformations. For client writers and more importantly for users, this would be a tremendous advantage to be able to make server-side requests using one syntax regardless of the underlying server implementation.

Statement of Work

Identify those implementations which offer server-side processing. Identify a common subset of processing requests. Develop a common mechanism for embedding the request into the URL and a common syntax for the identified processing types. Some candidate for requests that could have a common syntax are sum, average, minimum and maximum along one or more axes.

Members

  1. Roland Schweitzer
  2. Patrick West

Resources

--Roland Schweitzer (Mon Sep 24 14:21:10 CDT 2007)