THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| ID | IEP-66 |
| Author | |
| Sponsor | |
| Created |
|
| Status | DRAFT |
Motivation
Thin clients currently require manual binary configuration for settings like compact footer and simple/full name mapper, which is complicated and error-prone.
Description
Extend the protocol to retrieve those settings automatically on start.
Feature Flag
BINARY_CONFIGURATION bitmask feature flag lets the client know that binary configuration can be requested.
Operation
Name | Code |
|---|---|
OP_BINARY_CONFIGURATION_GET | 3004 |
| Request |
|---|
| (empty) |
| Response | |
|---|---|
| bool | compactFooter |
| byte | binaryNameMapperMode (0 = basic full name, 1 = basic simple name, 2 = custom) |
Assumptions
// TODO Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.
Discussion Links
// TODO Links to discussions on the devlist, if applicable.
Reference Links
// Links to various reference documents, if applicable.
Tickets
// Links or report with relevant JIRA tickets.
Overview
Content Tools
Apps
