Strategies for concurrent updates

49 views
Skip to first unread message

Guillermo López

unread,
Mar 9, 2017, 2:34:31 PM3/9/17
to SabreDAV Discussion
Hi,

I'm testing a simple SabreDAV deployment (only two users) with delegated accounts to share data (since I couldn't find a way to enable per-calendar sharing, http://sabre.io/dav/caldav-sharing/).

We are finding ourselves overwriting each other data because of concurrent updates too often. This is really preventing us from collaborating properly through SabreDAV. So my questions are:
  • Which component is responsible for proper concurrent updates? Client applications or the server?
  • Should we be using any specific client to prevent this situation? Currently we are using Lighting and DAVdroid.
  • Is there any configuration in the server that can be tuned to offer more reliability?

Thank you in advance,


Guillermo





Guillermo López

unread,
Mar 13, 2017, 3:36:57 PM3/13/17
to SabreDAV Discussion
Hello again,

I wonder whether I should be using calendar sharing instead of account delegation.

The calendar sharing plug-ins are enabled in my server, but I can't find a way to share a calendar through the web interface. Which tables do I have to modify in the database to share a calendar?

Thank you,

Guillermo
Reply all
Reply to author
Forward
0 new messages