RobluScouting / RobluTodo

A central location for feature requests, proposed designs, and discussion regarding the future of Roblu.
1 stars 0 forks source link

[Feat]: Syncing V6 Protocol #15

Open widavies opened 2 years ago

widavies commented 2 years ago

Design syncing protocol that is platform agnostic.

Syncing protocol should consider:

Syncing must also consider what to sync:

For maximum flexibility, all events should be synced all the time (remove the restriction of one active event). A team may archive an event to stop it from syncing, but it will naturally stop syncing if data is stopped being added to it. This would allow more use cases for teams who'd like to create multiple "Roblu event" objects for an event to separate out data. Maybe they contribute to another event for another team as well.

Further along, we might want to model "syncs" as "pull requests" that can have permissions (needs approval, anyone can merge, etc.). Especially if we want to support public events that anyone can make a "pull request" to.

Additionally, a better improvement to sync over legacy would be to NOT perform merging during the transfer, but to instead ONLY transfer data, close the connection & report sync as success, then merge at the receiver's leisure.

github-actions[bot] commented 2 years ago

Community Note: