public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.03)
Date: Thu, 11 Aug 2005 14:13:02 -0300	[thread overview]
Message-ID: <e1effdeb050811101346f4ddd6@mail.gmail.com> (raw)
In-Reply-To: <42F36564.9010505@palmsource.com>

Hi folks,


I am sending a new draft(v00.03) of the bluetoothd D-Bus interfaces.

BlueZ community, please send your feedback. I need collect your opinions
and discuss with Marcel.

The most important part for now is hci, hciconfig, sdp and bluetoothd.

The documents are available at:
http://www.cin.ufpe.br/~ckt/bluez/

Fred, thanks for your comment. I am not sure if is useful send
signal for connection/disconnection from hci. I think they should
be restricted to object hierarchy subsection(pan, dun, rfcomm, ..).
But we can discuss with the BlueZ community in order to verify if
these signals will be required or not.


Regards,
Claudio.


On 8/5/05, Frederic Danis <frederic.danis@palmsource.com> wrote:
> Hello Claudio,
>=20
> I think it could be usefull to get remote device
> connection/disconnection signal from hci.
>=20
> Regards,
> Fred
>=20
> -----------------------------------------------
> It is not by improving the oil lamp that one invents the electric bulb!
> -----------------------------------------------
> Danis Frederic            PalmSource Europe
> Software engineer
> Mail : mailto:frederic.danis@palmsource.com
> -----------------------------------------------
>=20
>=20
>=20
> Claudio Takahasi wrote:
>=20
> >Hi folks/Marcel,
> >
> >I am sending a new version of bluetoothd D-Bus interfaces document.
> >
> >When you have time, please look this document to see if the interfaces
> >names, object paths and services are following your ideas.
> >
> >The documents are available at:
> >http://www.cin.ufpe.br/~ckt/bluez/
> >
> >
> >Regards,
> >Claudio
> >
> >
> >-------------------------------------------------------
> >SF.Net email is Sponsored by the Better Software Conference & EXPO
> >September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practi=
ces
> >Agile & Plan-Driven Development * Managing Projects & Teams * Testing & =
QA
> >Security * Process Improvement & Measurement * http://www.sqe.com/bsce5s=
f
> >_______________________________________________
> >Bluez-devel mailing list
> >Bluez-devel@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/bluez-devel
> >
> >
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-08-11 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 19:40 [Bluez-devel] bluetoothd D-Bus interface proposals Claudio Takahasi
2005-08-05 13:11 ` Frederic Danis
2005-08-11 17:13   ` Claudio Takahasi [this message]
2005-08-17 16:18     ` [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.03) Frederic Danis

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=e1effdeb050811101346f4ddd6@mail.gmail.com \
    --to=cktakahasi@gmail.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