User:Mvl/offline: Difference between revisions
< User:Mvl
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
players: | players: | ||
# local ics calendar | |||
# observer | |||
# remote (ics) calendar | |||
# UI frontend | |||
The front-end applies all the changes to the local calendar. This can be done while offline, no problem. | The front-end applies all the changes to the local calendar. This can be done while offline, no problem.<br> | ||
The observer gets a note of all those changes, and stores them in a changelog. | The observer gets a note of all those changes, and stores them in a changelog.<br> | ||
Every few minutes, the observer tries to apply the changes to the remote calendar. (This might fail due to being offline. No problem, just try later.) Now that all local changes are uploaded, the remote file can be downloaded. With this new file, the local calendar can be re-filled. This way, the user will see the remote changes. | Every few minutes, the observer tries to apply the changes to the remote calendar. (This might fail due to being offline. No problem, just try later.) Now that all local changes are uploaded, the remote file can be downloaded. With this new file, the local calendar can be re-filled. This way, the user will see the remote changes. | ||
Latest revision as of 20:38, 19 April 2007
Offline
Example: ics provider.
players:
- local ics calendar
- observer
- remote (ics) calendar
- UI frontend
The front-end applies all the changes to the local calendar. This can be done while offline, no problem.
The observer gets a note of all those changes, and stores them in a changelog.
Every few minutes, the observer tries to apply the changes to the remote calendar. (This might fail due to being offline. No problem, just try later.) Now that all local changes are uploaded, the remote file can be downloaded. With this new file, the local calendar can be re-filled. This way, the user will see the remote changes.