Java Reference
In-Depth Information
same as for MSA 1.0; security requirements remain similar in principle but have
expanded considerably to include privileges for the additional APIs that MSA2 requires.
■
Caution
As I write this, JSR 249 is in draft form and is subject to change. Before you rely on the material
I provide here, visit the JCP web site for this JSR at
http://jcp.org/en/jsr/detail?id=249
to obtain
the latest copy and see if there are any changes that may affect your development plans.
Examining MSA2 Limited
MSA2 Limited is essentially MSA Subset 1.0, with only the minimum number of additions
to ensure common APIs across the lowest tier of multiple devices. It includes the Mobile
Internationalization API ( JSR 238) that MSA 1.0 requires, as well as the generic framework
for mobile device sensor management that JSR 256 defines.
The Mobile Sensor API gives you access to mandatory hardware sensors (the
battery and network-received signal strength) and a 3D accelerometer if the device
hardware has one.
Examining MSA2 Subset
MSA2 Subset builds on MSA2 Limited; in fact, it's a superset of MSA2 Limited. It must
provide support for the following packages:
•
MIDP 3.0
: Defined in JSR 271, MIDP 3.0 is a fundamental part of MSA2 Subset
and MSA2. Currently under development by members of the JCP, it will extend the
MIDP 2.1 APIs already present by adding support for shared library code, better
application life-cycle management, a secure binary interface for the inter-MIDlet
exchange of record stores, and enhanced user interfaces, including required
support for the MMAPI.
•
Mobile broadcast service
: Many devices today can receive broadcast content such
as digital television. JSR 272 defines interfaces to access the service guide (permit-
ting applications to search the database of program content) as well as render
broadcast content including subtitles or other metadata associated with broadcast
content using an API based on the MMAPI.
•
Contactless communication
: JSR 257 (which I mention in Chapter 15) describes
means of performing contactless communication to RFID cards or visual tags.
Support for this API is required if the underlying hardware provides these
facilities.
