Cross Transport API Spec
Define an API spec that supports extensions, versioning and that is also cross-transport. This will allow Zaqar to define its API in a single module and allow transport for translating the API to something supported by the protocol they implement.
It has been discussed during the Kilo summit that this feature will be implemented for non-RESTful transports. The WSGI transport won't be affected for this.
Blueprint information
- Status:
- Complete
- Approver:
- Flavio Percoco
- Priority:
- Medium
- Drafter:
- Flavio Percoco
- Direction:
- Needs approval
- Assignee:
- Victoria Martinez de la Cruz
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Flavio Percoco
- Completed by
- Flavio Percoco
Related branches
Related bugs
Sprints
Whiteboard
it won't be ready for i-3. Moving to Juno
Moving back to discussion, I believe this needs to be re-evaluated.
-- flaper87
This change is partially addressed by https:/
-- vkmc
Gerrit topic: https:/
Addressed by: https:/
Slighty refactoring for the cross api spec
Addressed by: https:/
API handler and API v1.1 endpoints
Addressed by: https:/
Refactor Request and Response classes to enhance consistency
Gerrit topic: https:/
Addressed by: https:/
Adds a status code field to the Response
Addressed by: https:/
Adds a representation for the Request and Response objects
Work Items
Dependency tree
* Blueprints in grey have been implemented.
