@Iain: yeah, I don't like having 2 storage and synchronization either.
I'm a bit reluctant since accountsservice was not really designed to be a config storage service and has downside compared to gsettings (no nice client API, reading involves hitting the bus and talking to a service (means relying on more code to be robust) ... I guess we should give it a try though
(bonus points if we make the telephony-service have fallback code in case something wrong happens with the config reading)
@Iain: yeah, I don't like having 2 storage and synchronization either.
I'm a bit reluctant since accountsservice was not really designed to be a config storage service and has downside compared to gsettings (no nice client API, reading involves hitting the bus and talking to a service (means relying on more code to be robust) ... I guess we should give it a try though
(bonus points if we make the telephony-service have fallback code in case something wrong happens with the config reading)