Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit LOCK members number to one #312

Open
carpawell opened this issue Dec 2, 2024 · 0 comments
Open

Limit LOCK members number to one #312

carpawell opened this issue Dec 2, 2024 · 0 comments
Labels
enhancement Improving existing functionality I2 Regular impact S2 Regular significance U3 Regular
Milestone

Comments

@carpawell
Copy link
Member

Is your feature request related to a problem? Please describe.

Same as in #311 but for LOCK objects. It is a little bit harder because there is no LOCK RPC and every LOCK object is created from scratch on the client side currently.

Describe the solution you'd like

It can also be restricted to one LOCK -- one LOCKed object. This also makes it more flexible for expiration and other side effects while LOCKing.

Describe alternatives you've considered

Keep it as is.

Additional context

Uncontrollable number of locked objects by a single object makes it harder to maintain object meta information: nspcc-dev/neofs-contract#448 (comment).

@carpawell carpawell added the I2 Regular impact label Dec 2, 2024
@roman-khimov roman-khimov added enhancement Improving existing functionality U3 Regular S2 Regular significance labels Dec 2, 2024
@roman-khimov roman-khimov added this to the v2.17.0 milestone Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality I2 Regular impact S2 Regular significance U3 Regular
Projects
None yet
Development

No branches or pull requests

2 participants