public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Implementing the PIN helper support
Date: Tue, 21 Feb 2006 11:31:18 +0200	[thread overview]
Message-ID: <20060221093118.GA10267@localhost.localdomain> (raw)
In-Reply-To: <1140471085.7047.63.camel@localhost>

Hi Marcel,

On Mon, Feb 20, 2006, Marcel Holtmann wrote:
> my current idea is to have a default handler that the applications have
> to register over org.bluez.Manager and that they can have multiple other
> PIN handlers registered via the org.bluez.Device interface for specific
> devices. While the default handler is permanent, all other PIN handlers
> may expire and get removed automatically.

I think you'll still need a way to unregister the default handler, when
e.g. a user logs out from his session (so the next user that logs in can
register his own default handler).

Using org.bluez.Manager interface for registering the default handler
seems to me extending too much its purpose compared to hald where we
copied it from. The only purpose of the manager interface there is to
allow local device discovery. Placing the default handler registration
method at the interface org.bluez.Device (or org.bluez.Device.PinAgent)
and object path /org/bluez/Device should be enough in my opinion. If you
want to register a handler only for a specific local device then the
exact path for that device (e.g. /org/bluez/Device/hci0) could be used.

> Do we really only need the object path? I really like to get the default
> handler thing implemented very soon.

For the handler registration the object path should be enough. However
we should probably rethink the org.bluez.PinAgent interface which
currently consists of only one method: PinRequest.

The PinRequest method currently takes two arguments: remote device
address and a boolean indicating whether the connection is incomming or
outgoing. A third parameter should probably be added for object path of
the local device, since that information could be used for e.g. querying
the name of the remote device.

Johan


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-02-21  9:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 20:44 [Bluez-devel] Implementing the PIN helper support Marcel Holtmann
2006-02-20 21:14 ` Johan Hedberg
2006-02-20 21:31   ` Marcel Holtmann
2006-02-21  9:31     ` Johan Hedberg [this message]
2006-02-21 11:35       ` Marcel Holtmann
2006-02-21 12:21         ` Johan Hedberg
2006-02-21 12:56           ` Marcel Holtmann
2006-02-21 12:40         ` Claudio Takahasi
2006-02-21 13:02           ` Johan Hedberg
2006-02-21 13:10             ` Marcel Holtmann
2006-02-21 13:02           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2006-02-20 20:48 Christopher E Piggott
2006-02-20 20:52 ` 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=20060221093118.GA10267@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