Changes between Version 4 and Version 5 of DRAFT_GAPI_AM_API_V2_DETAILS


Ignore:
Timestamp:
12/12/11 09:48:57 (12 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DRAFT_GAPI_AM_API_V2_DETAILS

    v4 v5  
    102102|| `ERROR`         || Internal error ||
    103103|| `SERVERERROR`   || Server error ||
    104 || `BUSY`          || Server busy; try again later ||
    105104
    106105==== Members of the !GetVersion {{{value}}} return struct ====
    … …  
    206205|| `FORBIDDEN`     || Credential does not grant permission to the slice ||
    207206|| `BUSY`          || Slice is temporarily locked, try again later ||
    208 || `BUSY`          || Server is temporarily busy, try again later ||
    209207|| `ERROR`         || Internal error ||
    210208|| `SERVERERROR`   || Server error ||
    … …  
    277275|| `ERROR`         || Internal error ||
    278276|| `SERVERERROR`   || Server error ||
    279 || `BUSY`          || Server is temporarily busy, try again later ||
    280277|| `BADVERSION`    || Bad Version of RSpec requested ||
    281278
    … …  
    315312|| `FORBIDDEN`     || Credential does not grant permission to the slice ||
    316313|| `BUSY`          || Slice is temporarily locked, try again later ||
    317 || `BUSY`          || Server is temporarily busy, try again later ||
    318314|| `ERROR`         || Internal error ||
    319315|| `SERVERERROR`   || Server error ||
    … …  
    367363|| `FORBIDDEN`     || Credential does not grant permission to the slice ||
    368364|| `BUSY`          || Slice is temporarily locked, try again later ||
    369 || `BUSY`          || Server is temporarily busy, try again later ||
    370365|| `ERROR`         || Internal error ||
    371366|| `SERVERERROR`   || Server error ||
    … …  
    441436|| `FORBIDDEN`     || Credential does not grant permission to the slice ||
    442437|| `BUSY`          || Slice is temporarily locked, try again later ||
    443 || `BUSY`          || Server is temporarily busy, try again later ||
    444438|| `ERROR`         || Internal error ||
    445439|| `SERVERERROR`   || Server error ||
    … …  
    574568|| 12   || SEARCHFAILED         || "Search Failed (eg for slice)" ||
    575569|| 13   || UNSUPPORTED  || "Operation Unsupported" ||
    576 || 14   || BUSY         || "Busy (resource, slice, or server); try again later" ||
     570|| 14   || BUSY         || "Busy (resource, slice); try again later" ||
    577571|| 15   || EXPIRED      || "Expired (eg slice)" ||
    578572|| 16   || INPROGRESS   || "In Progress" ||
    … …  
    581575Aggregates are similarly encouraged to provide hints on how to fix bad requests using the {{{value}}} entry to experimenters on error or failures. For example, a failed !RenewSliver call that failed because you are not allowed to renew your sliver that far in the future, might return a new date string in the {{{value}}} field that would be allowed. Similarly, a failed !CreateSliver call might return a modified request RSpec in the {{{value}}} field.
    582576
    583 Note that a malformed XML-RPC request should still raise an XML-RPC Fault, and other Faults dictated by the XML-RPC specification should still be raised.  Aggregates should avoid raising an error (XML-RPC Fault) for application layer errors or any other cases where the XML-RPC specification does not require a Fault, but rather should attempt to return this struct, providing any error messages and stack traces in the {{{output}}} field or other additional fields.
     577Note that a malformed XML-RPC request should still raise an XML-RPC Fault, and other Faults dictated by the XML-RPC specification should still be raised.  Aggregates should avoid raising an error (XML-RPC Fault) for application layer errors or any other cases where the XML-RPC specification does not require a Fault, but rather should attempt to return this struct, providing any error messages and stack traces in the {{{output}}} field or other additional fields.  Certain XML-RPC errors may be returned using Faults or otherwise by the XML-RPC layer, or may more properly be returned using this struct in the application layer. In such cases, servers should use error codes with negative values. Selected such errors are listed below:
     578
     579|| -32001       || SERVERBUSY   || "Server is (temporarily) too busy; try again later" ||
     580
     581Note also that servers may respond with other HTTP error codes, and clients must be prepared to deal with those situations. Specifically, a server that is busy might return HTTP code 503, or just refuse the connection.
    584582
    585583-----