From 3978df76ba5ecf7a774f27b02d53857a938c6abd Mon Sep 17 00:00:00 2001 From: Todd Baert Date: Tue, 29 Oct 2024 09:59:59 -0400 Subject: [PATCH] Update docs/reference/specifications/providers.md Co-authored-by: Guido Breitenhuber <157148191+guidobrei@users.noreply.github.com> Signed-off-by: Todd Baert --- docs/reference/specifications/providers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/specifications/providers.md b/docs/reference/specifications/providers.md index 3be8ada65..514892d7e 100644 --- a/docs/reference/specifications/providers.md +++ b/docs/reference/specifications/providers.md @@ -210,7 +210,7 @@ This pattern is consistent with OpenFeature's [static context paradigm](https:// The provider metadata includes properties returned from the [provider_ready event payload](./protos.md#eventstreamresponse) data. -## In-Process Providers +## In-Process Evaluation In-process providers use the [sync schema](./protos.md#syncflagsresponse) to connect to flagd, initiate the [sync stream](./protos.md#eventstreamresponse), and download the `flag-set` rules to evaluate them locally. In-process providers are relatively complex (compared to RPC providers) to implement since they essentially must implement more of flagd's logic to evaluate flags locally.