Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define structure of the information about subnetwork #180

Closed
cthulhu-rider opened this issue Nov 16, 2021 · 0 comments · Fixed by #183
Closed

Define structure of the information about subnetwork #180

cthulhu-rider opened this issue Nov 16, 2021 · 0 comments · Fixed by #183
Assignees
Labels
enhancement Improving existing functionality
Milestone

Comments

@cthulhu-rider
Copy link
Contributor

Summary

Information about subnetwork is stored and trasmitted between NeoFS components. It must have strict binary format and support
feature extensibility without losing backward compatibility. NeoFS API protocol messages are perfectly suited for this.

Task

Define SubnetInfo message structure (it can be placed in dedicated subnet package). It must consist of ID and owner ID (refs.OwnerID) fields. ID should be a separate type in order to describe its binary and string format. For now it should carry single numerical field. Both fields are required.

Note

ID definition is also required in #179.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants