Content deleted Content added
m →References: +cs |
Added BlueSoleil and BlueLet |
||
Line 6:
# ''General-purpose'' implementations that are written with emphasis on feature-richness and flexibility, usually for desktop computers. Support for additional [[Bluetooth profile]]s can typically be added through [[device driver|driver]]s.
# ''[[Embedded system]]'' implementations intended for use in devices where resources are limited and demands are lower, such as Bluetooth [[peripheral device]]s.
Only a single stack can be used at any time: switching usually requires uninstalling the current stack, although a trace of previous stacks remains in the registry.
==General-purpose implementations==
===Windows===
====BlueSoleil====
'''BlueSoleil''' is a product of the IVT Corporation, which produces stacks for everything from embedded devices to desktop systems. The API is freely available, and is probably the simplest and most powerful API to use. The stack is available in both standard and VOIP versions for [[Microsoft Windows|Windows]] desktop operating system. Mobile devices are supported by a separate version which supports DUN, FAX, HFP, HSP, LAP, OBEX, OPP, PAN and SPP. In addition to these profiles, the desktop version supports: AV, BIP, FTP, GAP, HID, SDAP, and SYNC. Of all the stacks, this has the most pleasant and intuitive user interface. '''BlueSoleil''' stacks can be downloaded with a 5MB data limit for evaluation purposes.
====WIDCOMM====
'''WIDCOMM''' is the first Bluetooth stack for the [[Microsoft Windows|Windows]] operating system. The stack was initially developed by a company named Widcomm Inc., which was acquired by [[Broadcom Corporation]] in April 2004.<ref name="widcomm-acquire">{{cite press release |date=2004-04-19 |title=Broadcom to Acquire WIDCOMM, the Industry's Leading Provider of Critical Software for Bluetooth® Wireless Devices |publisher=[[Broadcom]] |url=http://www.broadcom.com/press/release.php?id=515961 |accessdate=2007-03-02 }}</ref> Broadcom continues to [[license]] the stack for inclusion with many Bluetooth-powered [[end-user]] devices.
Line 17 ⟶ 21:
Prior to this, Microsoft released a [[QFE]] of its Bluetooth stack for [[Windows XP#Service Pack 1|Windows XP Service Pack 1]] labelled as QFE323183. Microsoft only released this directly to third-party companies and did not directly release it to the public. The third-party companies were then allowed to release the QFE as part of their own Bluetooth device's software installation. Microsoft no longer supports this QFE.
[[Windows Vista]] also includes a built-in Bluetooth stack which is an expansion over the [[Windows XP]] Bluetooth stack. In addition to supporting more [[Bluetooth profile]]s than Windows XP Service Pack 2, it also supports third-party driver development which enables third-parties to add support for additional Bluetooth Profiles. This was lacking in the Windows XP Service Pack 2 built-in Bluetooth stack, which only allowed application development on top of the Microsoft Bluetooth stack, which some observers felt slowed the adoption of the Microsoft Windows Bluetooth stack. In addition, the stack only supports a single SPP connection at any time, which is not always acceptable, consequently driving software vendors to use other stacks. By general consensus, API is the most clumsy of all those available: in particular a SPP connection does not return the serial port connected, leaving the programmer to query the registry to find which port was connected; this usually involves messy delay loops as the registry is updated before the port is actually available.
====Toshiba stack====
Line 33 ⟶ 37:
==Embedded implementations==
===BlueLet===
Also a product of IVT Corporation.
===lwBT===
'''lwBT''' is an [[open source]] lightweight Bluetooth protocol stack for [[embedded system]]s. It acts as a network interface for the lwIP protocol stack.
| |||