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
of course i can elaborate. Currently within the RPC mode we do have the EventStream, which will send on the inital connection a message provider_ready, and for upcoming messages configuration_change. This allows us within the RPC mode to be stateless. As flagd anyways knows when a configuration is established, or when it only informs about updates.
this would allow us to unify the logic, and keep both modes stateless. Currently we need to know, if we have been connected or not as we need to know, if we need to fire a configuration change or provider ready event.
I hope i could shed some light here, and i hope my motivation regarding this unification is clear
Originally posted by @aepfli in #1584
Requirements
type
, which carries same data as thetype
in https://buf.build/open-feature/flagd/docs/main:flagd.evaluation.v1#flagd.evaluation.v1.EventStreamResponse - on first stream payload, it should beprovider_ready
on subsequent payloads, it should beconfiguration_change
feat!: add sync stream type and context flagd-schemas#183The text was updated successfully, but these errors were encountered: