All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanyeol Park <chanyeol.park@samsung.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, 서호철 <hocheol.seo@samsung.com>,
	편도현 <dh79.pyun@samsung.com>
Subject: Re: How about adding Dbus log in gdbus?
Date: Mon, 12 Dec 2011 21:57:22 +0900	[thread overview]
Message-ID: <4EE5FA32.7070807@samsung.com> (raw)
In-Reply-To: <CABBYNZLCP=g4uKwDDOGt4mWw2YJ8c5+nUbTkD7YDyQ-miK8oyw@mail.gmail.com>

Hi
On 2011년 12월 10일 06:08, Luiz Augusto von Dentz wrote:
> Hi Chanyeol,
>
> 2011/12/9 Chanyeol Park<chanyeol.park@samsung.com>:
>> Hello
>>
>> How about adding dbus log in gdbus when we get method call from the remote
>> peer(application)?
>>
>> Personally It could be very useful for begginer.Based on it many people
>> could understand
>> call procedure easily. As far as I know this was removed when bluez 3.xx.
>> but compared to the days,
>> recently many dbus APIs have been introduced.
>>
>> But I know it is relatetd to many projects(bluez,obexd,connman,ofono).
>> So we need to consider a few things such as dependency managing and user
>> preference.
>> because curren gdbus does not have dependency with log.c/log.h.
>>
>> Is there good idea about this?
> Yes it is probably a good idea, but I would suggest we have some
> environment e.g. GDBUS_DEBUG to enable/disable it. Also while talking
> to Johan about this he suggested to have some function to register the
> callback/handler to log, so the projects using gdbus can register
> their own function.
Is it possible to relate this with bluez/obexd enable/disable debug feature?
Personally if we start to use environment variable(GDBUS_DEBUG), it 
would be difficult to use it.

Johan: Could you explain me what you think or suggest?

Thanks
Chanyeol Park


      reply	other threads:[~2011-12-12 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 15:39 How about adding Dbus log in gdbus? Chanyeol Park
2011-12-09 21:08 ` Luiz Augusto von Dentz
2011-12-12 12:57   ` Chanyeol Park [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE5FA32.7070807@samsung.com \
    --to=chanyeol.park@samsung.com \
    --cc=dh79.pyun@samsung.com \
    --cc=hocheol.seo@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.