Changes between Version 34 and Version 35 of PhyloWS_workgroup
- Timestamp:
- 2008/02/12 18:20:17 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PhyloWS_workgroup
v34 v35 37 37 38 38 === Inputs === 39 The input data types defined here do not imply pass-by-value, i.e. "One Tree" could be some kind of identifier 39 The input data types defined here do not imply pass-by-value, i.e. "One Tree" could be some kind of identifier. In addition, it looks like several services need multiple data types (e.g. a matrix + a tree, in order to return a tree score). Given that accumulate-and-fire (i.e. stateful operations, where you first post a matrix, then a tree) is a Bad Thing, and that tunneling multiple data types in a single attachment or body (e.g. a chunk of nexus/nexml) is also a Bad Thing, it seems that these combinations of data would be submitted as multiple post parameters. 40 40 * '''One Tree''' - exactly one tree, which might function as a query topology, as an input for topology metric calculations, or as something for which associated data (matrices) and metadata might be retrieved 41 41 * '''Pair of Trees''' - exactly two trees, which function as inputs for tree-to-tree distance calculations