Second,
JABWT implementations are able to differentiate themselves on the basis
of the policies the implementation enforces.
Because multiple applications are able to run and access the local
Bluetooth device at the same time, con?¬‚icting requests can be made to
the Bluetooth device. As far as JABWT is concerned, two types of requests
can con?¬‚ict with another application using the same Bluetooth device.
First, two applications may request different security settings on a link.
(Bluetooth security is described in Section 4.1.) Second, two applications
may request to set the device into two different discoverable modes.
(Discoverable modes are described in Chapter 6.) The BCC is responsible
for resolving these con?¬‚icting requests.
3.2.2 Modifying Device Properties
Although JABWT allows an application to retrieve certain properties of
the local device, no methods within JABWT allow direct modi?¬?cation of
a device??™s properties. In particular, setting of the friendly name, the class
of device record, the list of pre-known devices, the list of trusted devices,
the minimum security requirements, and support for the different connectable/
discoverable modes are handled by the BCC. (Each of these
concepts is described later in this book.) The friendly name is a userfriendly
name given to a Bluetooth device.
Pages:
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85