On Wed, 2009-09-09 at 11:20 +0100, Jussi Kukkonen wrote:
> Previously I used these dbus errors
> "org.Moblin.SyncEvolution.GenericError"
> "org.Moblin.SyncEvolution.NoSuchServer" -specified config does not
> exist
> "org.Moblin.SyncEvolution.MissingArgs" -should probably be InvalidArgs
> "org.Moblin.SyncEvolution.InvalidCall" -e.g. calling Abort when not
> syncing
>
> Of those I actually check for NoSuchServer and InvalidCall in the
> client.
I've add the following comment to the spec:
<doc:para>
Method calls may fail with the following errors:
"org.syncevolution.Exception" - catch-all error condition.
"org.syncevolution.NoSuchConfig" - server configuration name is invalid
"org.syncevolution.NoSuchSource" - source name is invalid
"org.syncevolution.InvalidCall" - a call is (perhaps no longer) allowed
or suitable in the current situation, like Detach() when the client
is not attached.
</doc:para>
org.syncevolution.Exception is already used in the new
syncevo-dbus-server, in all cases. So we need to turn some of the other
cases into more specific errors.
--
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
