Hi, On Tue, Jul 5, 2011 at 1:30 PM, Bartosz Szatkowski <bulislaw@xxxxxxxxx> wrote: > On Tue, Jul 5, 2011 at 12:13 PM, Luiz Augusto von Dentz > <luiz.dentz@xxxxxxxxx> wrote: >> Hi, >> >> On Tue, Jul 5, 2011 at 1:07 PM, Bartosz Szatkowski <bulislaw@xxxxxxxxx> wrote: >>> On Tue, Jul 5, 2011 at 11:58 AM, Luiz Augusto von Dentz >>> <luiz.dentz@xxxxxxxxx> wrote: >>>> Hi Bartosz, >>>> >>>> On Tue, Jul 5, 2011 at 12:00 PM, Bartosz Szatkowski <bulislaw@xxxxxxxxx> wrote: >>>>> >>>>> Don't know anything about it, but is there really any other choice? >>>>> >>>> >>>> I guess the idea is to use D-Bus directly, removing the ebook dependency. >>>> >>>> -- >>>> Luiz Augusto von Dentz >>>> >>> >>> And what the "original" problems with libebook was? So i could test it >>> further. BTW I'v tested this backend and it's working fine - no >>> problem with obexd itself either ... >> >> iirc it uses dbus-glib which once initialized replaces the gdbus >> callbacks, in other words D-Bus signals and method calls stop working >> for anything that is not using dbus-glib. >> >> >> -- >> Luiz Augusto von Dentz >> > > So for example signals would stop being emitted? It the receiving parts that becomes problematic, because the mainloop callbacks are know being handled by dbus-glib so any handler/watch using gdbus won't work. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
