Linux bluetooth development
 help / color / mirror / Atom feed
From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS-PATCH] list registered paths
Date: Fri, 14 Oct 2005 10:49:09 -0300	[thread overview]
Message-ID: <e1effdeb0510140649h6e9b504es2f1e76d2d622cad8@mail.gmail.com> (raw)
In-Reply-To: <1129293738.5057.61.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]

On 10/14/05, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Claudio,
>
> > The attached patch implements the service for list the registered
> > paths under the path /org/bluez/Manager.
> >
> > The message request signature can be:
> > 1. ListPaths() - list all paths under /org/bluez/Manager
> > 2. ListPaths(String), The string is the relative path. eg: "hci0",
> > "default" - list all paths provided by one adapter
>
> do we really need this?


[Claudio Takahasi]
How clients will discover the active paths if we change the format?
eg: "hci0" to "AA_BB_CC_DD_EE_FF"

The developers can use the dbus.h constants to compose the path, but if we
provide this service. It will be possible check if the path is active and/or
check if it provide a specific profile(pan,rfcomm).

When a client send a msg to a unregistered path, it will receive a reply
with "Device path is not registered" message.

I agree that at the moment this service is not much useful, the final
decision is yours :)


> Other minor changes:
> > - removed some logs
> > - added verification for dbus_connection_list_registered function. It
> > can return FALSE if there is no memory
> > to allocate the child entries
>
> Don't send combined patches. If you have cleanups then send them as a
> separate patch.


[Claudio Takahasi]
Ok. I will send soon.

Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>



--
---------------------------------------------------------
Claudio Takahasi
Nokia's Institute of Technology - INdT
claudio.takahasi@indt.org.br

[-- Attachment #2: Type: text/html, Size: 2993 bytes --]

      reply	other threads:[~2005-10-14 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 12:30 [Bluez-devel] [DBUS-PATCH] list registered paths Claudio Takahasi
2005-10-14 12:42 ` Marcel Holtmann
2005-10-14 13:49   ` Claudio Takahasi [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=e1effdeb0510140649h6e9b504es2f1e76d2d622cad8@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