There is an interesting thread on this subject dating back to July<br><br><a href="http://lists.openmoko.org/pipermail/openmoko-devel/2007-July/001081.html">http://lists.openmoko.org/pipermail/openmoko-devel/2007-July/001081.html
</a><br><br>Quite a long thread but interesting.<br><br>With regards,<br><br>Mark.<br><br><br><div><span class="gmail_quote">On 11/8/07, <b class="gmail_sendername">Chris Lord</b> <<a href="mailto:chris@openedhand.com">
chris@openedhand.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>On Thu, 2007-11-08 at 09:20 +0000, Ross Burton wrote:
<br>> On Thu, 2007-11-08 at 00:05 +0100, <a href="mailto:weppner@fim.uni-passau.de">weppner@fim.uni-passau.de</a> wrote:<br>> > Hi: I consider to implement a sychronization client on OpenMoko for e.g. PIM<br>> > Data. Could this be based on SyncML, OpenSync or something like that? How
<br>> > complex would be such a realization? Are there made any efforts on planning<br>> > sychronisation yet?<br>><br>> OpenMoko uses Evolution Data Server, so either opensync or syncevolution<br>> should work as a starting point.
<br><br>Last time I tried opensync it was a moving target and performance was<br>pretty terrible (in terms of speed/data corruption) - But I've no idea<br>what syncevolution is like either... There's also conduit.
<br><br>--Chris<br><br><br><br></blockquote></div><br>