On Thu, 2011-10-20 at 12:32 -0400, David Hampton wrote: > On Thu, 2011-10-20 at 09:17 +0200, Patrick Ohly wrote: > > But updating is recommended; you can install the .rpms from > > http://downloads.syncevolution.org/syncevolution/evolution/ > > Done. > > > Note that the HOWTO that you were using > > (http://syncevolution.org/wiki/http-server-howto) does not synchronize > > the data with Evolution. That's intentional, because it was meant for > > a server on the Internet without Evolution. See a second HOWTO if you > > want to synchronize with Evolution: > > http://syncevolution.org/wiki/synchronizing-evolution-evolution-http-howto > > That doesn't quite fit the model of what I'm trying to do since I only > have a single instance of evolution. Or can the client in those > instructions be any SyncML speaking device?
That is indeed the case. Use the same sync URL as for the SyncEvolution client and the "addressbook", "calendar", "todo", "memo" names as URIs. Should there be a third HOWTO covering the "phone <-> SyncEvolution HTTP SyncML server with Evolution" case or can you think of some changes to the existing HOWTOs which avoids the need for such a third one? > From a 10,000 foot level, my goal is to sync the data on my phone to > evolution running on my desktop without the data leaving the premises. > I don't want a copy of my data laying around in the internet on some > server that I don't control. I was hoping I could use the Synthesis > SyncML Client for Android to speak SyncML to the syncevolution http > server to accomplish this goal. That should work. I used the Android client for a while against a SyncEvolution HTTP SyncML server myself, for pretty much the same reasons. I only stopped because I switched to synchronizing against my work calendar and addressbook (via CalDAV and SyncML). > Any suggestions on how to make this > work? See above. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
