Is your feature request related to a problem? Please describe.
|
SplitInfo split_info = 3; |
|
SplitInfo split_info = 3; |
|
SplitInfo split_info = 2; |
are response body fields. In general, split info is a particular response payload. However, it is mutex with "normal" data - header and/or payload chunks. This makes it more of a response status
in Go SDK, https://pkg.go.dev/github.com/nspcc-dev/neofs-sdk-go/object#SplitInfoError is an error, and they are also kinda status
Describe the solution you'd like
dedicate new status code for split info.
itself will be a detail. Deprecate body field. Require servers to respond w/o body depending on the
|
neo.fs.v2.refs.Version version = 1 [json_name = "version"]; |
field
Describe alternatives you've considered
no more
Additional context
developing new object GET API
Is your feature request related to a problem? Please describe.
neofs-api/object/service.proto
Line 303 in cf4caf5
neofs-api/object/service.proto
Line 479 in cf4caf5
neofs-api/object/service.proto
Line 678 in cf4caf5
are response body fields. In general, split info is a particular response payload. However, it is mutex with "normal" data - header and/or payload chunks. This makes it more of a response status
in Go SDK, https://pkg.go.dev/github.com/nspcc-dev/neofs-sdk-go/object#SplitInfoError is an
error, and they are also kinda statusDescribe the solution you'd like
dedicate new status code for split info.
neofs-api/object/types.proto
Line 314 in cf4caf5
neofs-api/session/types.proto
Line 164 in cf4caf5
Describe alternatives you've considered
no more
Additional context
developing new object GET API