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

Resource tags optimistic locking #308

Open
lemon24 opened this issue Jun 4, 2023 · 0 comments
Open

Resource tags optimistic locking #308

lemon24 opened this issue Jun 4, 2023 · 0 comments

Comments

@lemon24
Copy link
Owner

lemon24 commented Jun 4, 2023

Some kind of locking is probably required to implement a use case like reactions (thumbs up/down etc., #228 (comment)) correctly. Use cases like implementing comments (with versions) might benefit too.

Optimistic locking seems like a reasonable enough solution.

(Note we don't need this for feeds/entries because they're more or less eventually consistent.)

Relevant resources:

Open questions:

  • What does the API look like?
    • Can we use a reserved top level key?
    • OTOH, reserved keys are for end-user-facing features...
      • But, is it reader's responsibility to control how they are shown? Presumably, for a use case like the one described above, the user would not see those tags directly, but see them rendered as 👍, 👎 anyway.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant