MIDP 2.0 is a revised version of the MIDP 1.0 specification. Includes new features such as an enhanced user interface, multimedia and game functionality, greater connectivity, over-the-air (OTA) provisioning, and end-to-end security. MIDP 2.0 is backward compatible with MIDP 1.0, and continues to target mobile information devices such as mobile phones and PDAs.
Includes new features such as an enhanced user interface, multimedia and game functionality, greater connectivity, over-the-air (OTA) provisioning, and end-to-end security. MIDP 2.0 is backward compatible with MIDP 1.0, and continues to target mobile information devices such as mobile phones and PDAs.
- Media Support:- MIDP 2.0 now includes the the Audio Building Block (ABB) that is also part of the Mobile Media API (MMAPI)
- Game Support:- MIDP 2.0 adds a Game API that provides a standard foundation for building games. The MIDP Game API includes game-specific functionality, such as sprites and tiled layers, that take advantage of native device graphics capabilities.
- Expanded Connectivity:- MIDP 2.0 adds support for leading connectivity standards beyond HTTP, such as HTTPS, datagram, sockets, server sockets, and serial port communication.
- Push Architechture:- With Release 2.0, MIDP now includes a server push model whereby MIDlets can be registered to be activated when a device receives information from a server. Application settings, which are a combination of default phone settings and end user settings, determine whether to prompt the user, start the MIDlet without prompting, or not start the MIDlet during the use of another MIDlet. The MIDP push architecture enables developers to leverage the event-driven capabilities of devices and carrier networks, and easily include alerts, messaging and broadcasts using a standard approach in MIDP applications.
- Over-the-air (OTA) Provisioning:- The MIDP specification defines how MIDlet suites are discovered, installed, updated and removed on mobile information devices. MIDP also enables a service provider to identify which MIDlet suites will work on a given device, and obtain status reports from the device following installation, updates or removal.
- End-to-end Security:- MIDP 2.0 adds a robust end-to-end security model, built on open standards, that protects the network, applications and mobile information devices. MIDP 2.0 supports HTTPS and leverages existing standards such as SSL and WTLS to enable the transmission of encrypted data. In MIDP 2.0, security domains protect against unauthorized access of data, applications and other network and device resources by MIDlet suites on the device. By default MIDlet suites are not trusted, and are assigned to untrusted domains that prevent access to any privileged functionality. To gain privileged access, a MIDlet suite must be assigned to specific domains that are defined on the mobile device, and must be properly signed using the X.509 PKI security standard. In order for a signed MIDlet suite to be downloaded, installed and granted associated permissions, it must be successfully authenticated.
