Re: Public API for Bluetooth Inquiry
Re: Public API for Bluetooth Inquiry
- Subject: Re: Public API for Bluetooth Inquiry
- From: Eric Brown <email@hidden>
- Date: Sat, 16 Nov 2002 11:29:04 -0800
On Saturday, November 16, 2002, at 07:29 AM, Paul Davis wrote:
To whom it may concern:
I know you have discussed this topic in recent threads but I would
like to
add my 2 cents. I spent 2 days reading your Bluetooth API documentation
trying to figure out how to do an inquiry without the GUI.
The application I am working on will involve using an OBEX connection
to
send data between client and server. I absolutely do not want the user
to
have to choose the device/service record in order for this to work. I
will
probably require the user to pair devices initially. However, after
this my
design requirement is to simply find the device and verify the service
I
need is available using SDP query. The user will not be aware of this
activity.
If you do require the user to pair, you can easily use the pairing
panel we provide (IOBluetoothPairingController) and then save off the
user's selection. We're also adding API to access the list of paired
devices so once that is in place, you could still find the device you
are interested in if the user used the pairing panel in the pref pane.
One problem with attempting to dynamically detect devices is that
performing an inquiry is a somewhat expensive and intrusive process.
Depending on what hardware is in use, connections can be completely
interrupted while the inquiry is in progress. Doing one while the user
isn't expecting it could be annoying at best.
Even if you have the user initiate the discovery process and then
perform SDP queries on each device to find the one (more than one?)
that has the service you are interested in, that process could be
rather lengthy if there are many discoverable devices around. It gets
even longer if any of the devices don't respond to the page/connection
process. With failed connections taking anywhere from 15 to 45
seconds, a discovery process like this in a dense environment could
easily run into several minutes.
In summary, the quicker I can have access to the inquiry API, the
better.
Any chance you can give a more definitive date addressing when the
stack
will be released with the inquiry API?
Unfortunately I can't comment on upcoming releases at this time.
- Eric
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.