mirror of
https://github.com/samsonjs/vdirsyncer.git
synced 2026-03-25 08:55:50 +00:00
Expand server support section in README
This commit is contained in:
parent
666fb7259c
commit
03b32f6c07
1 changed files with 19 additions and 6 deletions
25
README.rst
25
README.rst
|
|
@ -23,13 +23,26 @@ CardDAV/CalDAV Server Support
|
|||
=============================
|
||||
|
||||
vdirsyncer is currently tested against the latest versions of Radicale and
|
||||
ownCloud. While Radicale seems to work perfectly, ownCloud currently has
|
||||
problems detecting collisions and race-conditions. However, given that this is
|
||||
a problem with every setup involving ownCloud, and that ownCloud is widely
|
||||
used, it apparently isn't big enough of a problem yet.
|
||||
ownCloud.
|
||||
|
||||
See `Bug #16 <https://github.com/untitaker/vdirsyncer/issues/16>`_ for
|
||||
informations on problems with ownCloud.
|
||||
Radicale
|
||||
--------
|
||||
|
||||
Radicale doesn't `support time ranges in the calendar-query of CalDAV/CardDAV
|
||||
<https://github.com/Kozea/Radicale/issues/146>`_, so setting ``start_date`` and
|
||||
``end_date`` in vdirsyncer's configuration will have no or unpredicted
|
||||
consequences.
|
||||
|
||||
ownCloud
|
||||
--------
|
||||
|
||||
ownCloud uses SabreDAV, which had problems detecting collisions and
|
||||
race-conditions. The problems were reported and are fixed in SabreDAV's repo.
|
||||
See `Bug #16 <https://github.com/untitaker/vdirsyncer/issues/16>`_ for more
|
||||
information.
|
||||
|
||||
However, given that this is a problem with every setup involving ownCloud, and
|
||||
that ownCloud is widely used, it apparently isn't big enough of a problem yet.
|
||||
|
||||
How to use
|
||||
==========
|
||||
|
|
|
|||
Loading…
Reference in a new issue