This repository has been archived by the owner on May 30, 2024. It is now read-only.
4.0.0
[4.0.0] - 2018-05-10
Changed:
- To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option
inlineUsersInEvents
. For more details, see Analytics Data Stream Reference. - When sending analytics events, if there is a connection error or an HTTP 5xx response, the client will try to send the events again one more time after a one-second delay.
- The
LdClient
class is nowfinal
.
Added:
- New methods on
LDConfig.Builder
(updateProcessorFactory
,featureStoreFactory
,eventProcessorFactory
) allow you to specify different implementations of each of the main client subcomponents (receiving feature state, storing feature state, and sending analytics events) for testing or for any other purpose. TheComponents
class provides factories for all built-in implementations of these.
Deprecated:
- The
featureStore
configuration method is deprecated, replaced by the new factory-based mechanism described above.