Add split object meta into signed data #1255

New issue

Closed

opened 2025-12-28 17:22:21 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:22:21 +00:00

Owner

Originally created by @roman-khimov on GitHub (Sep 11, 2024).

Originally assigned to: @carpawell on GitHub.

I'm always frustrated when we can't easily untangle big object status based on meta info.

Describe the solution you'd like

Extend data added in #2928 to contain split id associated things. The goal is to have enough data to avoid network communication when processing big objects.

Originally created by @roman-khimov on GitHub (Sep 11, 2024). Originally assigned to: @carpawell on GitHub. ## Is your feature request related to a problem? Please describe. I'm always frustrated when we can't easily untangle big object status based on meta info. ## Describe the solution you'd like Extend data added in #2928 to contain split id associated things. The goal is to have enough data to avoid network communication when processing big objects.

sami

2025-12-28 17:22:21 +00:00

closed this issue
added the
enhancement

U3

I4

S3
labels

sami commented

2025-12-28 17:22:21 +00:00

Author

Owner

@carpawell commented on GitHub (Dec 12, 2024):

The goal is to have enough data to avoid network communication when processing big objects.

@roman-khimov, what is the exact use case here? The simplest thing is to try to put every part in the message. But the message could be really big then. Also, we now know that we try to minimize our our lists in the meta info. It may have first object ID, link object ID, or both but that is not "avoid network communication".

@carpawell commented on GitHub (Dec 12, 2024): > The goal is to have enough data to avoid network communication when processing big objects. @roman-khimov, what is the exact use case here? The simplest thing is to try to put every part in the message. But the message could be really big then. Also, we now know that we [try to minimize our](https://github.com/nspcc-dev/neofs-contract/pull/448#discussion_r1860489419) our lists in the meta info. It may have first object ID, link object ID, or both but that is not "avoid network communication".

sami referenced this issue

2025-12-28 17:23:01 +00:00

Make session storage use proper encryption keys #1444

sami referenced this issue

2025-12-28 17:23:01 +00:00

Merge persistent_sessions and persistent_state #1446