270
edits
| Line 318: | Line 318: | ||
==== Decisions to make==== | ==== Decisions to make==== | ||
* How we keep the local data model and server data model in sync? | * How we keep the local data model and server data model in sync? | ||
** [emre] I prefer 4th approach. I can't say I totally understand the overall system design yet but it seems doable. Here is the rationale: | |||
*** It doesn't require any change of the database schema | |||
*** It hooks into the following points: | |||
***# the point where TB retrieve the headers from the server, just before writing them into the database | |||
***# the point where TB generates fake keys for offline operations | |||
***# the point where UNDOing happens | |||
***# just before the system exits, to write the real keys into the database | |||
***# it's standalone and can be tested separately | |||
***# (do I miss anything else?) | |||
*** Requires no change of database implementation nor folder interaction | |||
=== 3) Background Message Send === | === 3) Background Message Send === | ||
edits