Control API passes addresses in stringified format #2980
Labels
enhancement
Improving existing functionality
I4
No visible changes
neofs-storage
Storage node application issues
S3
Minimally significant
U4
Nothing urgent
Is your feature request related to a problem? Please describe.
I'm always frustrated when I realize we have to parse addresses in control API just because we have string representations being used in the protocol.
Describe the solution you'd like
Use good old bytes, it's protobuf anyway. 32 for OID. 32 for CID. 64 for address.
Describe alternatives you've considered
Keeping as is, it works with some slight overhead.
Additional context
#2968
The text was updated successfully, but these errors were encountered: