Return-Path: MIME-Version: 1.0 In-Reply-To: References: <1309816301-18377-1-git-send-email-bulislaw@linux.com> Date: Tue, 5 Jul 2011 13:33:51 +0300 Message-ID: Subject: Re: [PATCH obexd 1/5] Change EDS backend to support multiple ebooks From: Luiz Augusto von Dentz To: Bartosz Szatkowski Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi, On Tue, Jul 5, 2011 at 1:30 PM, Bartosz Szatkowski wrote: > On Tue, Jul 5, 2011 at 12:13 PM, Luiz Augusto von Dentz > wrote: >> Hi, >> >> On Tue, Jul 5, 2011 at 1:07 PM, Bartosz Szatkowski wrote: >>> On Tue, Jul 5, 2011 at 11:58 AM, Luiz Augusto von Dentz >>> wrote: >>>> Hi Bartosz, >>>> >>>> On Tue, Jul 5, 2011 at 12:00 PM, Bartosz Szatkowski 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