Tickets :: Comment on [#3472] Kronolith acting as WebDav client

* Your Email Address
* Spam protection	Enter the letters below: .__ . . __ . .. . [__)\|\/\|/ `\|\/\|\|__\| [__)\| \|\__.\| \|\| \|
Comment	> webdav.php (last attachment) extends sql.php. All database operations > are done in sql.php. > > The function listEvents first calls saveUpdatesFromWebDAV, which > updates the local database with those UID:s that exists at the webdav > server but not in database. If the same UID:s exist on both places > and "some" of the attributes differ, the local database is updated. > > > > All operations that change the data in the local database are > executed in the following order: > > 1) call saveUpdatesFromWebDAV to recieve a fresh update from webdav > > 2) do the local database operation (update, new, change, delete, etc) > > 3) call saveUpdateToWebDAV to save the update back to the webdav server > > > > Note1: I have prepared, so that it should be easy to lock the webdav > resource in 1) and release the lock in 3) to aviod inconsistent > updates at the webdav server, but it's not done yet. > > > > Note2: The saveUpdatesFromWebdav maybe doesn't have to be updated > each time the calendar is listed. Maybe a refresh-button somewhere? > >
Attachment
Watch this ticket