Transport Layer: Client Interface

Registered by Jamie Hannaford

We need a common client interface, and abstract base client, for the library. This will be used for HTTP transactions, not service functionality.

It should support:

- All HTTP request methods
- Interaction with Request, Responses, Header and URL objects
- Different connection methods:
  - cURL
  - sockets
  - a way to fake connections (for testing)
- Persistent connections
- Connection pooling
- Streams
- OpenStack X-Auth-Token authentication
- Redirects
- SSL support
- Retry strategies (in response to cURL/HTTP errors, throttling, etc.)

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Jamie Hannaford
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.