Calendar:Cache: Difference between revisions

Calendar:Cache (view source)

116 bytes added , 4 June 2005

Confirmed users

503

edits

@@ Line 5: / Line 5: @@
 Additionally, it should be possible to access and modify calendar data while
-offline. Modifying the data means that there must be some changelog that can be
+offline. If the user can modify data while offline, there should be a log of those changes that can be applied to the remote (authorative) store when coming back online.
-replayed on the online data.
+Different, but related, problem is the problem of using one single ics file on a (webdav) server simultaniously from multiple clients. When trying to upload the ics file it might turn out that the external file has been modified. In that case, the changes made after the last succesful upload need to be re-applied to the new file, and uploaded again. Again, a changelog. If the cache can take care of this problem too, that would be a nice way to share code.
-A different, but related, problem is sharing a single ics file on a (webdav)
-server by multiple clients. When trying to upload, it might turn out that the
-external file has been modified. In that case, the changes since the last upload
-need to be re-applied to the new file, and uploaded again. Again, a changelog.
-If the cache can take care of this problem too, that would be a nice way
-to share code.
@@ Line 66: / Line 59: @@
 change, it can build a changelist and immidiatly remove the non-changed
 events from memory.
 = Implementation =