Patrick Ohly wrote:
On Wed, 2009-11-25 at 08:33 +0000, Jussi Kukkonen wrote:
Patrick Ohly wrote:
Should we change the semantic of the D-Bus API so that this is done
automatically? It would force users of the API to set it explicitly to 1
when wanted (command line?) and disable the user's configuration option
(unless the D-Bus client checks the config first itself).
Setting printChanges=0 in the client is not a big deal, but defaulting
to 0 (however that technically happens) in the D-Bus case makes sense to
me... I wouldn't expect a service to spend a lot of time outputting to
stdout.
Except when the client is the command line and we implement #5042: D-Bus
API: send log output to clients... That would include the output of
synccompare.
Yes, the point was a generic one: I didn't expect that to happen by
default.
For the sake of a clean design, would you mind setting printChanges=0
yourself?
Sure. I'll add a note to Session.Sync() docs, I'm pretty sure other
clients (if any) will want to do the same thing.
- Jussi
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
