client: Send request meta header once on object PUT stream init #257

New issue

Open

opened 2025-12-28 18:07:35 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:07:35 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Dec 10, 2024).

currently, Client attaches nspcc-dev/neofs-api@e66b25d4bf/session/types.proto (L162) to each ObjectService.Put stream message. Although this is not prohibited by the protocol, for chunks messages going after the heading one, this makes no sense. After header is accepted, storage node just reads incoming bytes and ignores meta fields

Describe the solution you'd like

set meta header in the 1st message only

Describe alternatives you've considered

keep and bear corresponding costs

Additional context

Client testing

Originally created by @cthulhu-rider on GitHub (Dec 10, 2024). ## Is your feature request related to a problem? Please describe. currently, `Client` attaches https://github.com/nspcc-dev/neofs-api/blob/e66b25d4bf2afc4472023e1e2c2467f694f5a0e1/session/types.proto#L162 to each [`ObjectService.Put`](https://github.com/nspcc-dev/neofs-api/blob/e66b25d4bf2afc4472023e1e2c2467f694f5a0e1/object/service.proto#L83) stream message. Although this is not prohibited by the protocol, for chunks messages going after the heading one, this makes no sense. After header is accepted, storage node just reads incoming bytes and ignores meta fields ## Describe the solution you'd like set meta header in the 1st message only ## Describe alternatives you've considered keep and bear corresponding costs ## Additional context `Client` testing