From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] pand D-Bus service
Date: Fri, 08 Jul 2005 21:08:01 +0200 [thread overview]
Message-ID: <1120849681.7444.1.camel@notepaq> (raw)
In-Reply-To: <e1effdeb05070811375af87810@mail.gmail.com>
Hi Claudio,
> We exchanged some emails last month about D-Bus services
> for pand. I implemented some D-Bus services, but ...
> How will be the relationship between the pand and the "metaserver"?
> It is not clear for me how the other daemons will
> interact with the current bluez-utils daemons and tools
> (pand, hidd, dund, rfcomm, ...).
forget about the metaserver. This is something KDE specific at the
moment.
> Could you explain me how the D-Bus services will be organized?
I am not 100% sure at the moment. Need to play with it a little bit
more.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-07-08 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 18:37 [Bluez-devel] pand D-Bus service Claudio Takahasi
2005-07-08 19:08 ` Marcel Holtmann [this message]
2005-07-11 18:54 ` Claudio Takahasi
2005-07-11 19:27 ` Marcel Holtmann
2005-07-11 20:16 ` Claudio Takahasi
2005-07-11 21:26 ` Marcel Holtmann
2005-07-12 17:07 ` Claudio Takahasi
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=1120849681.7444.1.camel@notepaq \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox