Symbian OS is not going to stop once it reaches full MSA but will keep
progressing and evolving because of the strategic importance of having a
powerful Java ME platform for Symbian OS.
We discussed consistency in Chapters 3 and 4, where we showed that
having a common implementation for many devices from many manufac-
turers ensures consistency in a remarkable way. Different models, from
different phone manufacturers have the same underlying implementation.
That is consistency.
Other MSA clarifications simply do not apply to Symbian OS. In
areas such as supported protocols, Java ME on Symbian OS exceeds
the requirements (e.g., by supporting TCP server sockets). In areas of
computing resources such as heap size and number of threads, Java ME
on Symbian OS does not set any fixed limits. As Java ME is hosted on
a powerful native operating system, application developers are free to
focus on the application task.
MSA supersedes JTWI and defines the next generation of Java ME platform
for mobile handsets based on MIDP/CLDC. It comprises a collection
of Component JSRs and additional clarifications and requirements that
define two MSA platforms: full MSA and MSA Subset.
MSA lets developers focus more on the main task of the application,
on the mobile service which the Java application enables, by providing a
rich and predictable Java ME environment.
We discussed building MusicMate, an application that uses the rich-
ness of MSA 1.1. Then we showed a few more examples and moved
to enhance an existing application, MobileAerith, with features that are
standardized in the MSA 1.1 specification.
The message should be clear, start writing great applications using