Open crabctrl opened 4 years ago
So after doing some work on #12, I'm just going to type up an overview of how the sync currently works.
It is split into three stages:
So in other words, this requires two read operations and two write operations. This might be annoying depending on the specific implementation (cough cough #4), but all in all it's pretty efficient and avoids us having to resend the entire database each time we sync.
We should have a single central class that handles the high-level sync stuff, so if we implement multiple sync interfaces (eg WiFi, QR codes, whatever) we don't have to rewrite the code every time.(moved to #12)Stuff we need to sync:
Match schedule/list of competitions (BA stuff)(see #9)Schedules(see #5)