Other
JABWT implementations may involve different components or have
their components layered in a different way from that shown.
3.1.2 Java Packages
As stated in Chapter 2, JABWT essentially de?¬?nes two separate APIs.
Hence two Java packages are de?¬?ned. The packages are as follows:
1. javax.bluetooth
2. javax.obex
The OBEX API is de?¬?ned independently of the Bluetooth transport layer
and is packaged separately. Each of the two Java packages represents a
separate optional package, the implication being that a CLDC implementation
can include neither of them, one of them, or both of them.
The javax.bluetooth package contains the Bluetooth API, and the
javax.obex package contains the APIs for OBEX.
Figure 3.2 shows the package structure. The javax.obex and
javax.bluetooth packages depend on the javax.microedition.io
package, which contains the GCF.
javax.obex
javax.microedition.io
javax.bluetooth
Figure 3.2 Package structure.
Architecture of JABWT 37
3.1.3 Client and Server Model
An overview of the Bluetooth client and server model is given in this
section. Additional details are provided in later chapters.
A Bluetooth service is an application that acts as a server and provides
assistance to client devices via Bluetooth communication. This assistance
typically takes theformof a capabilityor a function unavailable locallyonthe
client device.
Pages:
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78