From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Big rename for the D-Bus API
Date: Mon, 27 Feb 2006 09:38:35 +0200 [thread overview]
Message-ID: <20060227073835.GA16640@localhost.localdomain> (raw)
In-Reply-To: <1141022379.823.2.camel@localhost>
Hi Marcel,
On Mon, Feb 27, 2006, Marcel Holtmann wrote:
> I just came to the conclusion that using org.bluez.Device for the local
> attached Bluetooth dongles etc. is not a good name. I would prefer to
> use org.bluez.Adapter and start renaming everything before the next
> release. Any comments?
I'm fine with that. The current naming is because of the "let's imitate
hald interface" decision. However, if you change "Device" to "Adapter",
then I think that the methods and signals in the Manager path should
also change to using Adapter instead of Device (currently we have
ListDevices, DefaultDevice, DeviceAdded and DeviceRemoved).
Johan
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-02-27 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 6:39 [Bluez-devel] Big rename for the D-Bus API Marcel Holtmann
2006-02-27 7:38 ` Johan Hedberg [this message]
2006-02-27 7:48 ` Marcel Holtmann
2006-02-27 9:10 ` Johan Hedberg
2006-02-27 9:19 ` Marcel Holtmann
2006-02-27 8:57 ` Marcel Holtmann
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=20060227073835.GA16640@localhost.localdomain \
--to=johan.hedberg@nokia.com \
--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;
as well as URLs for NNTP newsgroup(s).