Re: [SyncEvolution] notes from design meetings last week

2009-09-24 Thread Zhu, Yongsheng
[mailto:syncevolution-boun...@syncevolution.org] On Behalf Of Patrick Ohly Sent: Wednesday, September 23, 2009 10:17 PM To: Jussi Kukkonen Cc: SyncEvolution Subject: Re: [SyncEvolution] notes from design meetings last week On Tue, 2009-09-22 at 16:51 +0100, Patrick Ohly wrote: My main takeaway

Re: [SyncEvolution] notes from design meetings last week

2009-09-24 Thread Patrick Ohly
On Thu, 2009-09-24 at 07:31 +0100, Zhu, Yongsheng wrote: Discussion ongoing on the list, reminder in Bugzilla: #6378 Together with implementation of DBus API, I'd like to take over this and discuss issues of design and implemenation with you. Is it ok? Okay, but let's finish the current work

Re: [SyncEvolution] notes from design meetings last week

2009-09-24 Thread Frederik Elwert
Am Mittwoch, den 23.09.2009, 11:32 +0300 schrieb Jussi Kukkonen: Conceptually I liked the idea of a small client that runs as a service and starts polling syncs and takes care of notifications. Practically it may make more sense to keep the dbus server running... Especially with

Re: [SyncEvolution] notes from design meetings last week

2009-09-23 Thread Jussi Kukkonen
Patrick Ohly wrote: On Wed, 2009-09-23 at 03:53 +0100, Zhu, Yongsheng wrote: Errors in this case are: * unexpected slow syncs * nothing else?! Mistakes in the backend? Yes, that's one possibility. It'll manifest itself in a failed sync. So how about suspending a source from syncing