Jump to: navigation, search

Difference between revisions of "Zaqar/specs/api/next"

(Generic)
(HTTP)
Line 19: Line 19:
 
* 204 vs. 200 + empty array
 
* 204 vs. 200 + empty array
 
* Consistency around response envelope for /messages vs /messages?ids
 
* Consistency around response envelope for /messages vs /messages?ids
 +
* Return full URIs in location/content-location headers (rather than relative ones)

Revision as of 16:30, 23 October 2013

Marconi API - Next

Brainstorming page for API improvements. The ideas below need to be discussed with the Marconi team and the OS community. They will be turned into blueprints as appropriate.

Generic

  • Auto-generate client UUID if not given
  • Clearly define whether client ID is required for every request, and enforce it in the implementation
  • Consider allowing opaque string for client ID rather than UUID (will need to understand what else people want to use?)
  • Remove deprecated "partial results" semantics from message posting
  • Include Client ID in claim data
  • Include claim information when listing messages and retrieving individual messages
  • List claims for a given queue

HTTP

  • Return an href for deleting all claimed messages with a single call
  • Allow PUTing metadata when creating a queue
  • 204 vs. 200 + empty array
  • Consistency around response envelope for /messages vs /messages?ids
  • Return full URIs in location/content-location headers (rather than relative ones)