Difference between revisions of "Zaqar/specs/api/next"
< Zaqar
(→Generic) |
(→Generic) |
||
Line 7: | Line 7: | ||
* Auto-generate client UUID if not given | * Auto-generate client UUID if not given | ||
* Clearly define whether client ID is required for every request, and enforce it in the implementation | * 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 | * Remove deprecated "partial results" semantics from message posting | ||
* Include Client ID in claim data | * Include Client ID in claim data |
Revision as of 21:10, 18 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