Client Configuration Reference
Ice Client is configured through constructor parameters. The following parameters have consistent semantics across the Java, Go, and Python SDKs.
Common Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
app | int | Yes | -- | App ID, corresponding to the App created in Server |
storagePath | string | Yes | -- | Shared storage path, must point to the same ice-data directory as Server |
scan | string | Java only | -- | Leaf node scan package path. Go/Python use explicit registration and do not need this parameter |
parallelism | int | No | -1 | Thread pool size for parallel nodes. <=0 uses framework default |
pollInterval | int/Duration | No | 5s | Version file poll interval |
heartbeatInterval | int/Duration | No | 10s (Java) / 30s (Go/Python) | Heartbeat reporting interval |
lane | string | No | empty | Lane name. Empty string means main trunk. Used for traffic isolation and branch testing |
Initialization Examples
Lane
Lanes are used for traffic isolation and are suitable for the following scenarios:
- Branch isolation testing in development environments
- A/B testing with different rule versions
- Canary releases
A Client with a lane configured will prioritize loading lane-specific configurations; nodes not configured in the lane fall back to the main trunk configuration.