[prev in list] [next in list] [prev in thread] [next in thread]
List: freedesktop-dbus
Subject: Re: DBus API problems & UTF-8
From: Kimmo =?ISO-8859-1?Q?H=E4m=E4l=E4inen?= <kimmo.hamalainen () nokia ! com>
Date: 2006-06-12 13:42:47
Message-ID: 1150119766.4967.189.camel () localhost ! localdomain
[Download RAW message or body]
On Mon, 2006-06-12 at 16:15, ext Thiago Macieira wrote:
> Kimmo Hämäläinen wrote:
> >> The solution would probably be to have a DBusError that is attached to
> >> that message and is set by any failing functions. This way, there
> >> would be no API changes, but it would allow you to obtain the error
> >> condition.
> >
> >You mean that the caller could check if the message is valid (no errors
> >happened) before sending it?
>
> No.
>
> I mean that current functions continue to return FALSE in case of errors,
> or -1 or whatever they do right now. If you need to understand the reason
> they failed, you inspect this member.
I assume you mean the DBusError parameter. Yes, in those cases there is
no problem.
> For object types that aren't connected to a message or DBusConnection
> (etc), they should return the reason for failure. I'm thinking of
> DBusString or similar simple types.
I would prefer a numeric value (since it's convenient and efficient to
handle in a switch clause), similar to the C library. How would you do
the API change then? Because if we just change it, the distributions
etc. would need to do a syncronised migration to the new API. Easier way
would be to have the new API co-exist with the old API for some time.
BR, Kimmo
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic