http://bugzilla.moblin.org/show_bug.cgi?id=7089
--- Comment #26 from pohly <patrick.ohly(a)intel.com> 2010-01-06 01:07:07 PST ---
(In reply to comment #25)
It seems to me that both dbus server and dbus client have to be aware
of
bluetooth service and handle many logics. I think maybe many logics and
processing are overlapped.
The D-Bus client doesn't have to implement much logic:
- get all configs and templates
- understand enough of syncURL to find the device it was invoked for
It does not talk to bluez directly, nor does it implement any kind of matching
logic.
Do you expect the GUI to do more than that? Where do you see an overlap in
functionality?
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.