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

Introduce ownership semantics for our handles #527

Closed
nirinchev opened this issue May 2, 2022 · 0 comments · Fixed by #876
Closed

Introduce ownership semantics for our handles #527

nirinchev opened this issue May 2, 2022 · 0 comments · Fixed by #876
Assignees

Comments

@nirinchev
Copy link
Member

nirinchev commented May 2, 2022

The RealmHandle should have the ability to own other handles and close them if necessary. Examples:

  1. Session handle - otherwise the session may outlive the Realm preventing deletion.
  2. SubscriptionSetHandle - same as 1.
  3. Object/List/Results handles when the Realm is unowned, e.g. migrations, initial data.

We can look at the .NET handle logic for inspiration.

@sync-by-unito sync-by-unito bot closed this as completed May 3, 2022
@nirinchev nirinchev reopened this Aug 22, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant