The concept of a named client was introduced in the v0.6.0 release. The goal was to add support for multiple providers so that they could be used within a single application. It worked by mapping clients to providers using the client name. While the functionality has proven to be very useful, the terminology used to describe the feature can be misleading and confusing.
Proposal
I suggest that we redefine the named client concept as domain. I think this term makes it clear that a user can leverage domains to map clients to providers.
Impact
This change should have little to no impact on the implementation within the SDKs. However, documentation will need to be updated accordingly. It will also require the SDK compatibility overview to be updated.
Overview
The concept of a named client was introduced in the v0.6.0 release. The goal was to add support for multiple providers so that they could be used within a single application. It worked by mapping clients to providers using the client name. While the functionality has proven to be very useful, the terminology used to describe the feature can be misleading and confusing.
Proposal
I suggest that we redefine the named client concept as
domain. I think this term makes it clear that a user can leverage domains to map clients to providers.Impact
This change should have little to no impact on the implementation within the SDKs. However, documentation will need to be updated accordingly. It will also require the SDK compatibility overview to be updated.