public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Moving towards a new API for BlueZ 4.0
Date: Fri, 14 Mar 2008 12:15:05 -0200	[thread overview]
Message-ID: <47DA8869.5030602@aircable.net> (raw)
In-Reply-To: <63E1C59E-6425-4B25-B5F2-44CF0107BADD@holtmann.org>

Marcel
> the new MacBooks suppose to have Bluetooth 2.1, but in case of  
> Extended Inquiry you need the new firmware (old hardware is okay) on  
> both sides. Haven't seen any of it in real life so far, but that is  
> what their specs say.
>   
Yeah me either, and I have some access to firmwares.

> In that specific case you would, but that is not the case we designed  
> the API for.
>   
I see.

> You get an additional DeviceFound which will then include the Name  
> value in the dictionary.
>   
Ok perfect, so then scanning with no name resolve makes no sense at all.

> As mentioned above. You get one (at least one) DeviceFound with no  
> Name value and a second one with the Name value.
>   
And I guess this one will be sended as soon as the old one was sent right?

> I am not sure. The code to make this all work is so complicated that I  
> really wanna remove it when we hit 4.0. Ping me again at some point.  
> For now we are going without allowing discovery without resolving the  
> name.
If this is the case, when we are still getting a callback as soon as the
device is discovered, and then another one with a resolved name it
doesn't harm the kind of applications I talk about.
What I'm most concerned off, and that's why I used no name resolving, is
that name resolving consumes connections, and we only have 7 per dongle.
And in some cases this is a real issue. In the past (well actually now a
days). What I do is first I scan with no name resolving, and then if I
don't know the device I go and ask the name, and then I go and ask for
the sdp records (I know I'm wasting connections and time).

But with this new API it will be even easier. I can't wait to start
getting my hands on it, and helping as much as I can (and my time allows
me). BTW what will happen with the old libbluetooth? I remember reading
some comments from you saying that 4.0 will remove all the hci commands,
will this be the case?

Cheers,
Manuel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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:[~2008-03-14 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 20:32 [Bluez-devel] Moving towards a new API for BlueZ 4.0 Marcel Holtmann
2008-03-14 10:23 ` Manuel Naranjo
2008-03-14 12:23   ` Marcel Holtmann
2008-03-14 13:44     ` Manuel Naranjo
2008-03-14 14:00       ` Marcel Holtmann
2008-03-14 14:15         ` Manuel Naranjo [this message]
2008-03-14 14:20         ` Robert Rawlins
2008-03-19 23:04 ` David Stockwell
2008-03-20 13:50   ` Marcel Holtmann
2008-03-20 14:49   ` Johan Hedberg

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=47DA8869.5030602@aircable.net \
    --to=manuel@aircable.net \
    --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