Use single layer of messages #70

Open
opened 2025-12-28 18:12:26 +00:00 by sami · 1 comment
Owner

Originally created by @cthulhu-rider on GitHub (Apr 21, 2022).

In current implementation we have 2 layers of messages:

  • so-called v2 layer with types providing stable marshaling
  • grpc layer with auto-generated types

After #389 generated messages provide stable marshaling, so we can purge v2 layer on type-level.

We also need to adopt rpc functionality.

Originally created by @cthulhu-rider on GitHub (Apr 21, 2022). In current implementation we have 2 layers of messages: * so-called v2 layer with types providing stable marshaling * grpc layer with auto-generated types After #389 generated messages provide stable marshaling, so we can purge v2 layer on type-level. We also need to adopt `rpc` functionality.
Author
Owner

@fyrchik commented on GitHub (Jun 30, 2022):

  1. This way we could lose the benefit from our previous optimizations #376 .
  2. Because now SDK uses v2 aliases in many places, we would need to implement similar wrappers in SDK. They can be more optimal there, though.
@fyrchik commented on GitHub (Jun 30, 2022): 1. This way we could lose the benefit from our previous optimizations #376 . 2. Because now SDK uses v2 aliases in many places, we would need to implement similar wrappers in SDK. They can be more optimal there, though.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-api-go#70
No description provided.