All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez+dbus: why glib binding
Date: Tue, 05 Feb 2008 18:08:17 +0100	[thread overview]
Message-ID: <1202231297.15090.109.camel@violet> (raw)
In-Reply-To: <f21e7dc80802050641pe208e9ew8eb686088cbf71d5@mail.gmail.com>

Hi Choi,

> > > If not - what do you use instead ? directly the libdus C lowlevel library ?
> > > or some other binding ?
> > > IOW - is it possible to use glib binding without dbus-glib ?
> >
> > You don't get it. The dbus-glib bindings are an integration of dbus into
> > the GObject model (libgobject). We don't use that. Yes, we use glib, but
> > not gobject and yes, we use dbus (low-level libdbus).
> 
> Ok, I think I understand.
> In bluez-utils, which is a d-bus server, you use directly the libdbus library,
> just like dbus-daemon does. So the glib is required for completely
> different reasons - not
> for using dbus. am I correct ?

we need the mainloop from glib to make dbus work. Otherwise we would
have to write our own mainloop and that is nasty.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-02-05 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  6:55 [Bluez-devel] bluez+dbus: why glib binding Choi Sonim
2008-02-05 14:13 ` Marcel Holtmann
2008-02-05 14:21   ` Choi Sonim
2008-02-05 14:29     ` Marcel Holtmann
2008-02-05 14:41       ` Choi Sonim
2008-02-05 17:08         ` Marcel Holtmann [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=1202231297.15090.109.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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.