6. Ability of applications to be both client and server to enable peerto-
peer networking. This is one of the vital use cases for Bluetooth
28 Chapter Two: An Overview of JABWT
wireless technology. One aspect of being a server is the ability to
register services for clients to discover. Although the Bluetooth
specification thoroughly addresses the client side of service
discovery, the mechanisms used by server applications to register
their services with a service discovery server are not standardized.
The JSR-82 expert group saw the need for defining service registration
in detail to standardize the registration process for the application
programmer.
7. Allowance for the possibility of building Bluetooth profiles on top
of the RFCOMM, L2CAP, and OBEX APIs. The expert group realized
that keeping up with the growing number of Bluetooth profiles
would be difficult (see Section 2.1.2).
2.2.2 Java ME Device Requirements
JABWT is not intended to be a complete solution by itself. It is an
optional API based on GCF and extends a Java platform to add support
for accessing Bluetooth wireless technology. As mentioned earlier, the
initial target devices are CLDC based. General Java ME device requirements
on which the API is designed to operate are listed below. More
detailed hardware requirements for various Java ME configurations and
profiles can be obtained from the respective specifications, which are
available at www.
Pages:
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69