ID | IEP-66 |
Author | |
Sponsor | |
Created |
|
Status | DRAFT |
Thin clients currently require manual binary configuration for settings like compact footer and simple/full name mapper, which is complicated and error-prone.
Extend the protocol to retrieve those settings automatically on start.
BINARY_CONFIGURATION bitmask feature flag lets the client know that binary configuration can be requested.
Name | Code |
---|---|
OP_BINARY_CONFIGURATION_GET | 3004 |
Request |
---|
(empty) |
Response | |
---|---|
bool | compactFooter |
byte | binaryNameMapperMode (0 = basic full name, 1 = basic simple name, 2 = custom) |
An alternative approach is to include this information into the handshake, which eliminates an extra request. However, a single partition-aware client performs a handshake with multiple server nodes. Binary configuration is guaranteed to be the same on all nodes in the cluster, so the client only needs to request it once. As a result, it is more efficient to perform one extra request than extending the handshake message.
// TODO Links to discussions on the devlist, if applicable.
// Links to various reference documents, if applicable.
// Links or report with relevant JIRA tickets.