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

OT algorithm and sharing system needs overhaul #272

Open
Luna-Klatzer opened this issue Jan 25, 2025 · 0 comments
Open

OT algorithm and sharing system needs overhaul #272

Luna-Klatzer opened this issue Jan 25, 2025 · 0 comments
Labels
bug Something isn't working critical Critical for the project or sprint

Comments

@Luna-Klatzer
Copy link
Contributor

Currently, the OT system is loosely based on a standard Delete & Insert OT system with no tracking of the cursor position or Retain command. Given that latency plays into the OT system in the deployed environment error correction is in its current form not properly working and generally, all transformations are applied indiscriminately without the ability to inverse or reverse transformations. Such functionality would be necessary though to allow for proper OT eventual consistency that ensures that all clients and the server have an identical state after all processing and information exchange is completed.

As such the current system needs to be overhauled and improved so that it can work properly similarly to other platforms like Google Docs or Microsoft Office, where multiple members can share and interact simultaneously.

@Luna-Klatzer Luna-Klatzer added bug Something isn't working critical Critical for the project or sprint labels Jan 25, 2025
@Luna-Klatzer Luna-Klatzer moved this to Todo in SolarDoc Jan 25, 2025
@Luna-Klatzer Luna-Klatzer pinned this issue Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working critical Critical for the project or sprint
Projects
Status: Todo
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant