Server-side Functions: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary
Line 17: Line 17:
* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/RHS-OPeNDAP_Dev_Con.ppt "Server-side OPeNDAP Analysis - A General Approach Utilizing Legacy Applications through TDS" ppt presentation to OPeNDAP Developer's meeting 2007]
* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/RHS-OPeNDAP_Dev_Con.ppt "Server-side OPeNDAP Analysis - A General Approach Utilizing Legacy Applications through TDS" ppt presentation to OPeNDAP Developer's meeting 2007]
* [http://www.iges.org/grads/gadoc/users.html The GrADS Data Server]
* [http://www.iges.org/grads/gadoc/users.html The GrADS Data Server]
* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/sld_WZJ07b.pdf SWAMP Presentation from the OPeNDAP Meeting]
* [http://dust.ess.uci.edu/ppr/ppr_WZJ073.pdf SWAMP Paper from Advances in Grid and Pervasive Computing, Second International Conference, GPC 2007]
* [http://wiki.opendap.org/twiki/bin/view/Developers/DevMeeting2007Program See this section 1445-1715 Server-Side Operations with 1530-1600 Break]
* [http://wiki.opendap.org/twiki/bin/view/Developers/DevMeeting2007Program See this section 1445-1715 Server-Side Operations with 1530-1600 Break]


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

Revision as of 19:26, 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
  3. Rob De Almeida

Resources

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