nspcc-dev / nspcc-dev/neofs-node
Unify network endpoints in single type
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
NeoFS SDK works with network endpoints in one way, Storage nodes with another (pkg/network package). After #1353 NeoFS CLI defined internal NetAddr type as a mediator.
Proposal
Leave a single type for network address information (network.Address) which provides methods for all needs. Maybe we need to place it in SDK?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing endpoint handling in the pkg/network package, the NeoFS SDK, and storage nodes, then inspect the CLI's internal NetAddr type introduced after #1353. Determine the common network.Address API and whether it belongs in the SDK. Done means the involved components use one address type for all required network endpoint operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100