Subscribing to flag changes

The client uses an event pattern which allows your app to subscribe to feature flag changes in real time.

To subscribe to feature flag changes, register listeners for change events from the SDK:

To learn more, read IFlagTracker.

The client uses a listener pattern which allows your app to subscribe to feature flag changes in real time.

To subscribe to feature flag changes, register listeners for change events from the SDK:

The flag key passed to onFeatureFlagChange is the key of the updated flag, which lets a single listener be registered for multiple flags.

You can also disable listeners by unregistering them:

Additionally, we provide an update listener interface for when you want to be notified when the flag cache is updated. The application provides a class implementing LDAllFlagsListener which provides the SDK with the method onChange. Whenever the SDK's flag cache is updated, it calls the onChange method with a list of flag keys for flags that were updated during the update to the flag cache. If no flag values changed, this list is empty.

Here is an example:

The client exposes an interface which allows your app to subscribe to feature flag changes in real time.

To subscribe to feature flag changes, register listeners for change events from the SDK:

If you are working in C, there are a few more steps:

1. Define a callback to receive the flag change notification:

   C++ SDK v3.0 (C binding), define callback

2. Assign the callback by creating a listener connection:

   C++ SDK v3.0 (C binding), create listener connection

3. Ensure the connection is freed when you are done with it:

   C++ SDK v3.0 (C binding), free connection

To learn more, read FlagNotifier.

The client uses an event emitter pattern which allows your app to subscribe to feature flag changes in real time.

To subscribe to feature flag changes, register listeners for change events from the SDK:

Or, you can listen for all feature flag changes:

Subscribing to change events automatically turns on streaming mode, unless you have explicitly set streaming to false.

The client uses an observer pattern which allows your app to subscribe to feature flag changes in real time.

To subscribe to feature flag changes, register listeners for change events from the SDK:

flagChanges is a stream that emits all flag changes, so you can use a single listener for multiple flags.

You can disable listeners by unregistering them:

You can also use flagChanges if you want to be notified any time the flag cache is updated. The application provides a callback that is activated whenever the SDK receives new flag data from the service. It calls with a list of flag keys that were updated. If no flag values changed, this list is empty.

To learn more, read flagChanges.

The client uses an observer pattern which allows your app to subscribe to feature flag changes in real time. To subscribe to feature flag changes, register listeners for change events from the SDK.

The SDK provides methods for listening to a single flag, all flags, or no change to any flag. observeFlagsUnchanged is called when the SDK successfully receives an update or comes back online but no flags have changed. If the value of the flag changes, the method executes the handler. It passes in the changedFlag containing the old and new flag values, and old and new flag value source.

The SDK retains only weak references to the owner, which lets the client app freely destroy owners without issues. Client apps should use a capture list specifying [weak self] inside handlers to avoid retain cycles causing a memory leak.

The SDK executes handlers on the main thread. LDChangedFlag does not know the type of oldValue or newValue. The client app should cast the value into the type needed.

To configure the client:

The client uses an event emitter pattern which allows your app to subscribe to feature flag changes in real time.

To subscribe to all feature flag changes, register listeners for change events from the SDK:

The settings object contains a map of updated feature flag keys and values. The map only contains the keys to flags that have changed. You can also subscribe to specific flags.

Here's how:

The client uses an event emitter pattern which allows your app to subscribe to feature flag changes in real time.

To subscribe to all feature flag changes, register listeners for change events from the SDK:

The allChanges object contains a map of updated feature flag keys and values. The map only contains the keys to flags that have changed. You can also subscribe to specific flags.

Here's how:

The client uses an event emitter pattern which allows your app to subscribe to feature flag changes in real time. The available event types include error and change.

To subscribe to all feature flag changes, register listeners for change events from the SDK. Here's how:

You can also disable listeners by unregistering them:

To learn more, read on and off.

The SDK provides an event-based mechanism to notify you when flag configurations change. LDClient.FlagTracker returns an interface for this mechanism, IFlagTracker.

Any event handler that you add to the IFlagTracker.FlagChanged event will be called with a FlagChangeEvent whenever there is a change in any feature flag's configuration, or in anything else that could indirectly affect the flag value, such as a prerequisite flag or a segment that the flag uses.

The event data consists only of the flag key. It does not contain a flag value, because in server-side SDKs, there is no such thing as a flag value except when it is evaluated for a specific context.

The listener method is called synchronously from a background task.

Here's how:

To listen for changes in flag values for a specific flag key and context, use IFlagTracker.FlagValueChangeHandler(). It calls your code with a FlagValueChangeEvent. This is equivalent to re-evaluating the flag for that context whenever there is a change in that flag. Because flag values can have different data types, the value is reported using the general type LdValue.

The Go SDK provides a channel-based mechanism to notify you when flag configurations change. The LDClient.GetFlagTracker() method returns an interface for this mechanism called FlagTracker.

Calling GetFlagTracker().AddFlagChangeListener() provides a channel that receives a FlagChangeEvent whenever there is a change in any feature flag's configuration. These changes include anything that could indirectly affect the flag value, such as a prerequisite flag or a segment that the flag uses.

The event data consists only of the flag key. It does not contain a flag value, because in server-side SDKs, flags only have values when they are evaluated for a specific evaluation context.

To listen for changes in flag values for a specific flag key and context, use GetFlagTracker().AddFlagValueChangeListener(), which provides FlagValueChangeEvents. This is equivalent to re-evaluating the flag for that context whenever AddFlagChangeListener() reports a change in that flag. Because flag values can have different data types, the value is reported using the general type ldvalue.Value.

With both of these methods, it is the caller's responsibility to consume values from the channel. Letting values accumulate in the channel can cause an SDK goroutine to be blocked.

The SDK provides a listener-based mechanism to notify you when flag configurations change. The LDClient.getFlagTracker() method returns an interface for this mechanism, FlagTracker.

Calling getFlagTracker().addFlagChangeListener calls your listener with a FlagChangeEvent whenever there is a change in any feature flag's configuration, or in anything else that could indirectly affect the flag value, such as a prerequisite flag or a user segment that the flag uses.

The event data consists only of the flag key. It does not contain a flag value, because in server-side SDKs, there is no such thing as a flag value except when it is evaluated for a specific set of user properties.

The listener method is called from a worker thread.

Here's how:

To listen for changes in flag values for a specific flag key and context, use getFlagTracker().addFlagValueChangeListener, which provides FlagValueChangeEvents. This is equivalent to re-evaluating the flag for that context whenever addFlagChangeListener() reports a change in that flag. Because flag values can have different data types, the value is reported using the general type LDValue.

The SDK provides an event-based mechanism to notify you when flag configurations change.

For example, imagine you have a feature flag named flag-key-123abc. If the SDK detects a change in flag-key-123abc's configuration, or in anything else that could indirectly affect the flag value, such as a prerequisite flag or a user segment that flag-key-123abc uses, it emits two events.

These events are:

• "update" and
• "update:flag-key-123abc"

You can listen for "update:flag-key-123abc" if you only want to know about updates affecting that flag specifically, or "update" if you want to be notified about all updates.

For both of these event kinds, an extra parameter is sent to event listeners. This object has the single property key, with its value set to the flag key. If you listened for the general "update" event, this lets you know which flag changed.

The event parameter does not contain the flag value. In server-side SDKs, there is no such thing as a flag value except when it is evaluated for a specific set of user properties.

To find out what the effect, if any, of the configuration change was, call variation() after receiving an update event.

Here is an example:

The SDK provides a listener-based mechanism to notify you when flag configurations change. The LDClient#flag_tracker method returns an interface for this mechanism, FlagTracker.

Calling flag_tracker.add_listener calls your listener with a FlagChange event whenever there is a change to any of the following:

• the flag's configuration
• the prerequisite flag's configuration
• a segment used by the flag

The event data consists only of the flag key. It does not contain a flag value, because server-side SDKs only evaluate flags when you provide a specific context.

The listener method is called from the caller's thread.

Here's how:

To listen for changes in flag values for a specific flag key and context, use flag_tracker.add_flag_value_change_listener, which provides FlagValueChange events. This is equivalent to re-evaluating the flag for that context whenever add_listener reports a change in that flag.

The SDK provides a listener-based mechanism to notify you when flag configurations change. The LDClient#flag_tracker method returns an interface for this mechanism, FlagTracker.

Calling flag_tracker.add_listener calls your listener with a FlagChange event whenever there is a change to any of the following:

• the flag's configuration
• the prerequisite flag's configuration
• a segment used by the flag

The event data consists only of the flag key. It does not contain a flag value, because server-side SDKs only evaluate flags when you provide a specific context.

The listener method is called from a worker thread.

Here's how:

To listen for changes in flag values for a specific flag key and context, use flag_tracker.add_flag_value_change_listener, which provides FlagValueChange events. This is equivalent to re-evaluating the flag for that context whenever add_listener reports a change in that flag.

You can use Roku's observeField method on your node to respond to changes in flags.

Here's how: