We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The system could have a built in secondary presence which only tracks user interaction with entities by OID.
Each replica has a lastUpdatedEntity tracked presence field which is seamlessly set to the latest OID to show up in their operations chronologically.
Maybe also a field name for objects?
Then Entities can expose a recent replicas list directly which includes all replicas that have modified them lately.
Requires more thought before implementation.
Use case: easily showing user presence in forms or other general live use cases.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The system could have a built in secondary presence which only tracks user interaction with entities by OID.
Each replica has a lastUpdatedEntity tracked presence field which is seamlessly set to the latest OID to show up in their operations chronologically.
Maybe also a field name for objects?
Then Entities can expose a recent replicas list directly which includes all replicas that have modified them lately.
Requires more thought before implementation.
Use case: easily showing user presence in forms or other general live use cases.
The text was updated successfully, but these errors were encountered: