public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Claudio Takahasi <cktakahasi@gmail.com>
Subject: Re: [Bluez-devel] [PATCH] Attempt bonding with keyboards.
Date: Sat, 22 Sep 2007 22:00:47 +0100	[thread overview]
Message-ID: <1190494847.7150.242.camel@pmac.infradead.org> (raw)
In-Reply-To: <1190487435.5133.66.camel@aeonflux.holtmann.net>

On Sat, 2007-09-22 at 20:57 +0200, Marcel Holtmann wrote:
> the main questions is if we wanna make that policy of pairing a device
> first part of the input service or the the UI creating the device.
> 
> I think it should be part of the UI and it should create the pairing
> before connecting the input device.

I'm not convinced. Should the UI really have to know things like 'if
it's a keyboard, attempt pairing. If it's a mouse, don't bother'?

I would have thought that this was something we should leave to the
input service. The UI just tells the service to make it work.

-- 
dwmw2


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-09-22 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22 17:49 [Bluez-devel] [PATCH] Attempt bonding with keyboards David Woodhouse
2007-09-22 18:57 ` Marcel Holtmann
2007-09-22 21:00   ` David Woodhouse [this message]
2007-09-22 23:10   ` David Woodhouse

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=1190494847.7150.242.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=cktakahasi@gmail.com \
    /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