On Wed, 2009-09-02 at 14:30 +0100, Jussi Kukkonen wrote:
> Unresolved issues:
> * anything else I may have forgotten?
We haven't discussed password handling across D-Bus yet. I think we can
add this later (clients set "-" in the SetConfig hashes, provide
password on request via the still to be defined engine<->client(s)
query/response API).
Also one minor change to the API: the config hashes should use "" for
the main config and "sources/<name of source>" as key for individual
source configs. That is a 1:1 mapping to the config tree (no special
cases in the implementation). It will allow us to extend the config
("peers/my_wonderful_bluetooth_device") in the future without changing
the API.
--
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
