Thus JABWT
can be ported to any Java platform that supports the GCF. The first two
characteristics below resulted from this thinking. JSR-197 adds the GCF
into Java SE platforms and will help JABWT and other Java ME APIs to be
usable on other Java platforms.
The characteristics of the JABWT specification are as follows:
1. Require only CLDC libraries.
2. Scalability??”ability to run on any Java platform that supports the
GCF.
3. OBEX API definition independent of Bluetooth protocols. By
contrast, applications written with the Bluetooth API are expected
to run only on platforms that incorporate Bluetooth wireless technology.
While defining the API for OBEX, the expert group recognized
that OBEX could be used over a number of different
transports (e.g., IrDA, USB, TCP). Therefore, the OBEX API is
defined to be transport independent. The OBEX API is in a separate
javax.obex package.
4. Use of the OBEX API without the Bluetooth API. An IrDA device
could implement the javax.obex package and not implement the
javax.bluetooth package, which contains the Bluetooth API.
5. Prevent applications from interfering with each other. The
concept of the Bluetooth Control Center (BCC), discussed in
Chapter 3, was introduced for this reason. The intent of the BCC
is to allow multiple Bluetooth applications to run simultaneously
and be able to access Bluetooth resources.
Pages:
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68