maryjane/syncevolution
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

added warnings about known-problems

Browse source 
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@74 15ad00c4-1369-45f4-8270-35d70d36bdcd
This commit is contained in:
Patrick Ohly 2006-04-17 17:28:07 +00:00
parent 1e2cd0cc19
commit 4ba87699c8
1 changed files with 19 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
README
View file

@ -10,7 +10,7 @@ There's no home page yet. Please refer to the SourceForge page instead:
http://sourceforge.net/projects/sync4jevolution/ http://sourceforge.net/projects/sync4jevolution/
Because the original name "sync4jevolution" is not really appropriate, Because the original name "sync4jevolution" is not really appropriate,
it was changed to SyncEvolution. The web page and project name will it was changed to SyncEvolution. The web page and project name will
be changed, too. be changed eventually, too.
Introduction Introduction
@ -173,6 +173,10 @@ the same server database with multiple local databases, one has
to setup two independent configurations with different "deviceId" to setup two independent configurations with different "deviceId"
settings and synchronize them separately. settings and synchronize them separately.
WARNING: either the server or the client library currently get
confused when multiple databases are synchronized at once. Better
avoid this at the moment.
If the Evolution data source requires authentication, the If the Evolution data source requires authentication, the
"evolutionuser" and "evolutionpassword" are used as credentials. In "evolutionuser" and "evolutionpassword" are used as credentials. In
this case the directory that contains the source's config.txt should this case the directory that contains the source's config.txt should
@ -233,6 +237,12 @@ for contacts and
uri = cal uri = cal
for calendars in the source config. for calendars in the source config.
WARNING: the current Sync4j 2.3 cannot parse calendar entries
as send by SyncEvolution. Until these issues are resolved in the
server, one has to fall back to a setup where the server does not
have to convert tasks. This is similar to the configuration for
tasks described in the next paragraph.
Although Evolution tasks are sent and received as special calendar Although Evolution tasks are sent and received as special calendar
events, the server cannot parse them. Therefore it is necessary to events, the server cannot parse them. Therefore it is necessary to
store each task as files on the server without having the server parse store each task as files on the server without having the server parse
@ -435,6 +445,14 @@ http://forge.objectweb.org/tracker/?group_id=96&atid=100096
ObjectWeb #304805, #304562 ObjectWeb #304805, #304562
- calendar conversion fails resp. loses information
ObjectWeb #304946, #304993, #304994, #304995, #304996, #304997
- synchronizing multiple databases at once does not correctly
set the status of the items in the right database; still needs
to be investigated
- Removing a field and then synchronizing with the Sync4j server - Removing a field and then synchronizing with the Sync4j server
will not remove that field on the server. The server will preserve will not remove that field on the server. The server will preserve
the old value instead. the old value instead.