Re: Broadcom Bluetooth SDK/API and Winsock
- From: Jimmy Bluetooth <JimmyB@xxxxxxxxxxxxxxxxx>
- Date: Tue, 24 Jul 2007 15:21:48 -0500
smartjohn62@xxxxxxxxx wrote:
Is this true? Am I forced to use lower level API calls to communicate
with the Bluetooth device>
After being spoiled with the simplicity and east of using Microsoft's
Winsock API for Bluetooth, it seems almost cruel to re-write
everything using Broadcom's interface.
I'm familiar with both the Broadcom interface and the Microsoft interface. For my project, I chose to use virtual serial ports instead of the socket interface. Virtual serial ports turned out to be finicky (especially when Bluetooth adapters get unexpectedly removed), and Microsoft communicated to me that they did not have any plans to improve their usability. In hindsight, I should have gone with sockets. I don't know enough details to answer your question directly, but I would recommend you stick with the sockets interface for the Microsoft stack regardless of how you end up supporting Broadcom's stack. And look long and hard for an answer to your question before giving up and going with the virtual serial port interface.
- JB
.
- References:
- Broadcom Bluetooth SDK/API and Winsock
- From: smartjohn62
- Broadcom Bluetooth SDK/API and Winsock
- Prev by Date: Re: Infinite loop with wsaasyncselect
- Next by Date: LSP (Layered Service Provider) with IE
- Previous by thread: Broadcom Bluetooth SDK/API and Winsock
- Next by thread: Re: How to programmatically Read/Write/Delete DNS Resolver Cache objec
- Index(es):
Relevant Pages
|
