freesmartphone.org dbus error specifications
Michael 'Mickey' Lauer
mickey at vanille-media.de
Tue May 13 18:14:41 CEST 2008
Hi, thanks for your comments!
> What about something like:
> org.freesmartphone.GSM.SIM.AuthFailed: PIN code is not accepted
> org.freesmartphone.GSM.SIM.AuthFailed: SIM is locked. PUK code is required
Agreed -- that sounds better than mine.
> So the interface used and the interface in the error may be different,
> e.g. all timeouts
> are reported as org.freesmartphone.GSM.Device.Timeout, right? We have
> always matched the interfaces and only changed the error part, but I think
> allowing them
> them to differ is better.
Exactly. By allowing them to differ, we have less redundancy and can limit the
number of exceptions our calling clients need to act to.
> I think that at least some kind of internal error code is also needed ;)
That's for sure. There's no way around the dbus server keeping a bit of state
> Have you thought whether it is mandatory to fully implement all APIs?
Yeah, it does not make sense to require implementing the full API. Some things
like the feature phone stuff (battery/vibrator/key control) and also the some
modem specific commands which may appear sooner will have to be optional.
> If it's not
> then some kind of "unsupported" error might be useful too.
Agreed. Let's use 'org.freesmartphone.GSM.UnsupportedCommand' for now.
Dr. Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
More information about the smartphones-standards