public class ClientSideConfig extends Object
ProxyManager such as:
backwardCompatibleWith(Version) for more details.withClientClock(TimeMeter) for more details.| Modifier | Constructor and Description |
|---|---|
protected |
ClientSideConfig(Version backwardCompatibilityVersion,
Optional<TimeMeter> clientSideClock) |
| Modifier and Type | Method and Description |
|---|---|
ClientSideConfig |
backwardCompatibleWith(Version backwardCompatibilityVersion)
Returns new instance of
ClientSideConfig with configured backwardCompatibilityVersion. |
Version |
getBackwardCompatibilityVersion()
Returns the Bucket4j protocol version is used to be backward compatible with other nodes in the cluster.
|
Optional<TimeMeter> |
getClientSideClock()
Returns clock that will be used for time measurement.
|
static ClientSideConfig |
getDefault()
Returns default client-side configuration for proxy-manager that configured with following parameters:
Client-clock: is null.
|
ClientSideConfig |
withClientClock(TimeMeter clientClock)
Returns new instance of
ClientSideConfig with configured clientClock. |
public static ClientSideConfig getDefault()
Versions.getLatest(). This means that compatibility with legacy versions is switched off.public ClientSideConfig backwardCompatibleWith(Version backwardCompatibilityVersion)
ClientSideConfig with configured backwardCompatibilityVersion.
Use this method in case of rolling upgrades, when you want from already new nodes to continue communication using
the legacy protocol version which is compatible with backwardCompatibilityVersion.
By default backward compatibility version is Versions.getLatest(). This means that compatibility with legacy versions is switched off.
backwardCompatibilityVersion - the Bucket4j protocol version to be backward compatible with other nodes in the cluster.ClientSideConfig with configured backwardCompatibilityVersion.public ClientSideConfig withClientClock(TimeMeter clientClock)
ClientSideConfig with configured clientClock.
Use this method when you want to measure current time by yourself. In normal scenarios you should not use this functionality, but sometimes it can be useful, especially for testing and modeling.
By default client-clock is null. This means that server-side clock is always used.
clientClock - the clock that will be used for time measuring instead of server-side clock.ClientSideConfig with configured clientClock.public Optional<TimeMeter> getClientSideClock()
withClientClock(TimeMeter)public Version getBackwardCompatibilityVersion()
backwardCompatibleWith(Version)Copyright © 2022. All rights reserved.