The MIDP version 2.0 is the result of a Java Community Process expert group
JSR-118
consisting of a number of industrial partners. See links for details.
The MIDP 2.0 specification defines an enhanced architecture and the associated APIs needed for application development for mobile information devices.
| MIDP | |
| CLDC | Libraries |
| KVM | |
| Host Operating System | |
The MIDP is a set of APIs that reside on top of the CLDC, providing features such as user interface, networking support and persistent storage. The MIDP 2.0 specification is based on the MIDP 1.0 specification, providing backwards compatibility so that MIDlets written for MIDP 1.0 can execute in MIDP 2.0 environments.
Requirements for display, input and networking are the same as for MIDP 1.0. Memory requirements have been raised in the MIDP 2.0 specification. There must be 256 KB of non-volatile memory for the MIDP implementation, beyond what's required for the CLDC and 128 KB of volatile memory for the Java runtime. Requirements for sound have been added. The ability to play tones is now made a requirement.
MIDP 2.0 is backwards compatible with MIDP 1.0, hence it provides all functionality defined in the MIDP 1.0 specification. In addition it provides Over-The-Air (OTA) provisioning. This feature was left to OEMs to provide in the MIDP 1.0 specification.
An enhanced user interface has been defined, making applications more interactive and easier to use.
Media support has been added through the Audio Building Block (ABB), giving developers the ability to add tones, tone sequences and WAV files even if the Mobile Media API (MMAPI) optional package is not available.
Game developers now have access to a Game API providing a standard foundation for building games. This API takes advantage of native device graphic capabilities.
MIDP 2.0 adds support for HTTPS, datagram, sockets, server sockets and serial port communication.
Push architecture is introduced in MIDP 2.0. This makes it possible to activate a MIDlet when the device receives information from a server. Hence, developers may develop event driven applications utilizing carrier networks.
End-to-end security is provided through the HTTPS standard. The ability to set up secure connections is a leap forward for MIDP programming. A wide range of application models require encryption of data and may now utilize the security model of MIDP 2.0 based on open standards.
Specifications, APIs and other MIDP-related information can be found at:
http://java.sun.com/products/midp/
This page was last updated 14. Jul. 2006
Comments and feedback are highly appreciated.
You can reach me at: klings (at) nowires (dot) org