8:29 a.m.
I just read the Data conversion and testing page on the wiki
(http://syncevolution.org/development/data-conversion-testing)
A number of scenarios are covered, but the one which
currently interests me is the preservation of unique fields
across clients...the last test scenario covered on the wiki page.
Apparently the Synthesis library is quite capable in this regard and
so Syncevolution should be robust as well.. provided that 1) (as
mentioned in the second scenario on the page) that the XML that defines
mapping from native to internal synthesis server format is complete and
2) that the server accurately advertise their capabilities
I'm still reviewing the source code and getting my head around the
architecture... but I think I'd like to look at the XML and/or
the code segments which advertise capabilities....
The syncevolution scenario of interest to me is: N900 with gui front-end
and HTTP server setup of syncevolution on the "server" ie: desktop side.
Actually, if someone has reviewed the N900 with HTTP server use case
already, then I might be more assured - perhaps I'm worrying too much.
Thank you for your thoughts...
--Jeff
5:39 a.m.
On Sat, 2010-04-24 at 23:29 +0100, Jeffrey Perry wrote:
Apparently the Synthesis library is quite capable in this regard and
so Syncevolution should be robust as well.. provided that 1) (as
mentioned in the second scenario on the page) that the XML that defines
mapping from native to internal synthesis server format is complete and
2) that the server accurately advertise their capabilities
Right.
I'm still reviewing the source code and getting my head around
the
architecture... but I think I'd like to look at the XML and/or
the code segments which advertise capabilities....
I can only speak for the contact backend, as the calendar backend was
done by Ove. With contacts in EDS, I know that "contact lists" are not
synchronized (http://bugs.meego.com/show_bug.cgi?id=1008). The main
reason is that there is no standard format commonly understood between
SyncML peers. When using SyncEvolution on both sides, that isn't a
problem, and something that works in that combination could be added.
On the N900, there are like to be some Nokia extensions which are not
synchronzed. I don't know what the situation is with those in Maemo 5,
but earlier there were such extensions
(http://bugs.meego.com/show_bug.cgi?id=666).
Actually, if someone has reviewed the N900 with HTTP server use case
already, then I might be more assured - perhaps I'm worrying too much.
I think you are the first one to look into it in that level of detail.
To put you at ease a bit, the automatic database dumps made by
SyncEvolution do not pass the data through the Synthesis engine. They
take a vCard directly out of EDS and put them into files, so the
complete contacts can be restored again should something go wrong.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9:09 a.m.
I can only speak for the contact backend, as the calendar backend was
done by Ove. With contacts in EDS, I know that "contact lists" are not
synchronized (http://bugs.meego.com/show_bug.cgi?id=1008). The main
reason is that there is no standard format commonly understood between
SyncML peers. When using SyncEvolution on both sides, that isn't a
problem, and something that works in that combination could be added.
I don't mind if contact lists don't sync as long as they are not lost
on the evolution side during sync.
My interest is in a syncevolution to syncevolution case...
You say "something that works in that combination could be added"
I'm confused by that ... what needs to be added?
On the N900, there are like to be some Nokia extensions which are
not
synchronzed. I don't know what the situation is with those in Maemo 5,
but earlier there were such extensions
(http://bugs.meego.com/show_bug.cgi?id=666).
Fields that don't exist at one side should be ignored as Synthesis does.
Is this what happens? or does data get lost as a consequence?
> Actually, if someone has reviewed the N900 with HTTP server use
case
> already, then I might be more assured - perhaps I'm worrying too much.
I think you are the first one to look into it in that level of detail.
Ok
To put you at ease a bit, the automatic database dumps made by
SyncEvolution do not pass the data through the Synthesis engine. They
take a vCard directly out of EDS and put them into files, so the
complete contacts can be restored again should something go wrong.
Please tell me a bit more about these backups and at what stage of the
sync process they are made and where they are located...
If I understand you correctly, you mean in the syncevolution with http
server configuration connecting with a syncevolution client (such as the
N900), data traveling to the client is taken straight from the EDS and
placed directly into files on the client.
So Synthesis is not part of the process?
4529
days inactive
4530
days old
syncevolution@synevolution.org
2 comments
3 participants
participants (3)
-
Jeff -
Jeffrey Perry -
Patrick Ohly