Require at least one field of `object.SplitInfo` to be set #72

New issue

Closed

opened 2025-12-28 18:12:24 +00:00 by sami · 1 comment

sami commented

2025-12-28 18:12:24 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (May 17, 2022).

In current implementation protocol doesn't impose restrictions on the presence of fields in object.SplitInfo message in ObjectService service. However, the absence of all fields is an incorrect response: it is not enough just to beacon about a fragmented object, you need to give a hook to the assembly.

Proposal

Require at least one field to be set.

P.S. proposal breaks backward compatibility of the protocol, however, this requirement was always implied and was simply not explicitly stated.

Originally created by @cthulhu-rider on GitHub (May 17, 2022). In current implementation protocol doesn't impose restrictions on the presence of fields in `object.SplitInfo` message in `ObjectService` service. However, the absence of all fields is an incorrect response: it is not enough just to beacon about a fragmented object, you need to give a hook to the assembly. ## Proposal Require at least one field to be set. P.S. proposal breaks backward compatibility of the protocol, however, this requirement was always implied and was simply not explicitly stated.