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, cktakahasi@gmail.com
Subject: [Bluez-devel] bluetoothd specification
Date: Tue, 12 Jul 2005 17:47:38 -0300	[thread overview]
Message-ID: <e1effdeb05071213476bbc0fa0@mail.gmail.com> (raw)

Hi Marcel,

Periodic inquiry and adapter setup is extremely
necessary for me. Is it possible set a high priority
for these features?

Regarding the interfaces and objects path of the=20
bluetoothd my suggestion is:

>>>bluetoothd
DBus service :    org.bluez.hci
DBus interface:   org.bluez.hci
DBus object path: org/bluez/hci
    - setup link properties
    - setup inquiry mode
    - kill bluetoothd
    - show local adapters
    - ???
>>>SDP
DBus service :    org.bluez.sdp
DBus interface:   org.bluez.sdp
DBus object path: org/bluez/sdp
methods:
    - search
    - register/unregister
    - get local services
    - ???

>>>PAN
DBus service :    org.bluez.pan
DBus interface:   org.bluez.pan
DBus object path: org/bluez/pan
    - connect/disconnect
    - listen start/stop
    - connections


Open issues:
- How/Where handle multiple bluetooth adapters?
  solution1: the device id (hci0) can be part of object path
  eg: org.bluez.hci0.pan org.bluez.hci0.sdp
            =20
  solution2: pass the device id as parameter or define a method=20
             to set the active adapter.


I am not sure if it is better define a hierarchical objects or
register multiples objects. Dbus support two functions:
dbus_connection_register_object_path and=20
dbus_connection_register_fallback(for a given subsection of the=20
object hierarchy). But I think that it is not important now because
for both approachs the message handler functions are distinct.
I will investigate more which approach is the best.

Defining an hierarchical approach make easier define policy/rules
in the dbus configuration files.=20

Do you have a different design for it or suggestions?
There are a lot services that shall be inserted in the bluetoothd,
maybe should be better define multiple interfaces(adapter, link, ... )=20
for this daemon.


Regards,
Claudio.


-------------------------------------------------------
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

             reply	other threads:[~2005-07-12 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 20:47 Claudio Takahasi [this message]
2005-07-15 17:37 ` [Bluez-devel] Re: bluetoothd specification Claudio Takahasi
2005-07-18 16:12   ` Frederic Danis
2005-07-18 16:46     ` Claudio Takahasi
2005-07-26 16:31       ` [Bluez-devel] Re: bluetoothd specification - new patch Claudio Takahasi
2005-07-26 17:18         ` Marcel Holtmann
2005-07-26 19:06           ` Claudio Takahasi
2005-07-26 21:57             ` Marcel Holtmann
2005-07-28 14:08               ` 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=e1effdeb05071213476bbc0fa0@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