You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| ✅ |[Targeting](#targeting)| Contextually-aware flag evaluation using [evaluation context](https://openfeature.dev/docs/reference/concepts/evaluation-context). |
106
106
| ✅ |[Hooks](#hooks)| Add functionality to various stages of the flag evaluation life-cycle. |
107
107
| ✅ |[Logging](#logging)| Integrate with popular logging packages. |
108
-
| ✅ |[Domains](#domains)| Logically bind clients with providers application.|
108
+
| ✅ |[Domains](#domains)| Logically bind clients with providers. |
109
109
| ❌ |[Eventing](#eventing)| React to state changes in the provider or flag management system. |
110
110
| ✅ |[Shutdown](#shutdown)| Gracefully clean up a provider during application shutdown. |
111
111
| ✅ |[Extending](#extending)| Extend OpenFeature with custom providers and hooks. |
The OpenFeature SDK logs to the `openfeature` logger using the `logging` package from the Python Standard Library.
191
191
192
-
### Named clients
192
+
### Domains
193
193
194
-
Named clients are not yet available in the Python SDK. Progress on this feature can be tracked [here](https://github.com/open-feature/python-sdk/issues/125).
194
+
Clients can be assigned to a domain.
195
+
A domain is a logical identifier which can be used to associate clients with a particular provider.
196
+
If a domain has no associated provider, the global provider is used.
0 commit comments