Unify REP and EC code in GET server implementation #1555

New issue

Open

opened 2025-12-28 17:35:51 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:35:51 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Dec 26, 2025).

This duplicates some logic we already have in the service (assembly_v2.go) which will add maintenance cost and headache. We need more code reuse for split assembly.

Originally posted by @roman-khimov in https://github.com/nspcc-dev/neofs-node/pull/3754#discussion_r2647143272

code is quite outdated, and many updates have been added on top of it, only adding to its complexity. The EC was the largest, so it was added nearby. It is proposed to perform a general code refactoring in careful, small steps. The secondary goal is to share the common logic between REP and EC.

Originally created by @cthulhu-rider on GitHub (Dec 26, 2025). This duplicates some logic we already have in the service (`assembly_v2.go`) which will add maintenance cost and headache. We need more code reuse for split assembly. _Originally posted by @roman-khimov in https://github.com/nspcc-dev/neofs-node/pull/3754#discussion_r2647143272_ code is quite outdated, and many updates have been added on top of it, only adding to its complexity. The EC was the largest, so it was added nearby. It is proposed to perform a general code refactoring in careful, small steps. The secondary goal is to share the common logic between REP and EC.