openstack-sdk-dotnet

Consider removing service locator functionality

Registered by Sam Harwell

The service registration and location functionality (implemented in the Openstack.Common.ServiceLocation namespace) is likely over-engineered for this SDK. Rather than complicate the construction of objects in this manner, the SDK should consider the use of construction (e.g. the way HttpClient provides a constructor with an HttpMessageHandler parameter) over service location to simplify the implementation and documentation of the SDK.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Sam Harwell
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/consider-removing-composition,n,z

Addressed by: https://review.openstack.org/91181
    Adding support for per-client-instance extensibility. See: https://wiki.openstack.org/wiki/OpenStack-SDK-DotNet/HighLevelArch for more details. Updated the example code project to be in sync with the api. Cleaned up a few style/comment issues, and move ar

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.
Edit subscription

Subscribers

No subscribers.