The spec now supplies the bound domain to a provider's initialize function, and adds an opt-in domain-scoped provider declaration that the API enforces by binding such a provider to at most one domain. This lets stateful providers (e.g. an OFREP static-context provider with a persistent cache) scope their state to a single, unambiguous domain.
What needs to happen
- Pass the bound
domain (if any) to the provider's initialization when it's registered via the provider mutator
- Extend
InitializeAsync to accept the optional domain (non-breaking, additional optional parameter)
- Add a way for a provider to declare itself
domain-scoped
- Enforce that a
domain-scoped provider is bound to at most one domain, rejecting any attempt to bind an already-bound instance to another domain
- Associated testing and docs
Links
The spec now supplies the bound
domainto a provider'sinitializefunction, and adds an opt-indomain-scopedprovider declaration that the API enforces by binding such a provider to at most onedomain. This lets stateful providers (e.g. an OFREP static-context provider with a persistent cache) scope their state to a single, unambiguousdomain.What needs to happen
domain(if any) to the provider's initialization when it's registered via the provider mutatorInitializeAsyncto accept the optionaldomain(non-breaking, additional optional parameter)domain-scopeddomain-scopedprovider is bound to at most onedomain, rejecting any attempt to bind an already-bound instance to anotherdomainLinks