Changes between Version 3 and Version 4 of GEC12GeniAmAPI

Timestamp:

11/03/11 17:28:14 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

GEC12GeniAmAPI

@@ -32 +32 @@
  * We agreed to two change sets, completing the list of changes to include in AM API version 2. We will:
  * Adopt change set A for inclusion in AM API version 2: RSpecs are GENI schema XML
- * Adopt change set B for inclusion in AM API version 2: 
+ * Adopt change set B part 1 for inclusion in AM API version 2: 
   * All methods include a new 'options' XMLRPC struct argument with no required values, supporting aggregate innovation
+ * We expect to also include set B part 2 in API version 2, assuming we can quickly address a few outstanding questions:
   * All methods return an XMLRPC struct consisting of (1) a return 'code', (2) the return 'value' from API v1, and (3) a human readable 'output' on errors, plus optional aggregate specific entries
- * Discuss details on some parts of change set B
+ * We will continue to discuss details on some parts of change set B part 2, to finalize AM API version 2:
   * This discussion to continue at the coding sprint
   * Error codes: integers? or strings? (including a specific namespace rather than the more discrete and arbitrary integers)
@@ -48 +49 @@
 === Selected Discussion Points ===
  * Change set A (RSpecs are XML) was adopted without discussion
- * Change set B (new options argument and new return structure) was adopted with minor discussion.
+ * Change set B part 1 (new options argument) was adopted with minor discussion.
+ * Change set B part 2 (methods return XMLRPC structs) has a few minor open questions, and should be in API version 2 if we can resolve these issues shortly:
   * We must agree to and document GENI error codes
   * Error codes were proposed as integers, with the space divided by aggregate developer. That either wastes codes or limits or both, while also hiding in a translation table whose codes these are. Why not use strings?