Sorry, ran out of time on my last post. Here's the important extract from the Mobile Internet WP.
"Sun has worked with device manufacturers to improve the fit of Java in consumer devices. The result is the Java 2 Micro Edition (J2ME) architecture, which is modular and scalable so that it can support the kind of flexible deployment demanded by the consumer and embedded markets. For low-end, resource-limited products, J2ME uses an optimized virtual machine known as the KVM. It supports minimal configurations of the Java virtual machine and Java APIs that capture just the essential capabilities of each type of device.
J2ME uses the concept of configurations and profiles to create application portability for entire classes of devices. A configuration is defined as a set of optimized Java APIs, class libraries and a Virtual Machine (VM) targeting a family of devices with similar requirements on size and capabilities. Configurations include components of the java.io, java.net, java.util, and the java.lang packages.
A profile is a collection of Java technology-based class libraries and APIs and a specific configuration that provides domain-specific capabilities for devices in a specific vertical market such as cell phones, set top boxes, and PDAs.
Sun has worked closely with NTTDoCoMo in Japan, as well as leading mobile phone OEMs such as Motorola, Siemens and Nokia, to develop a configuration specification for mobile phones. The configuration specification is known as the Connected, Limited Device Configuration (CLDC), and the associated profile is known as the Mobile Information Device (MID) Profile. The European Telecommunications Standards Institute (ETSI) is watching closely. It is likely that the specification will become part of the Mobile Station Application Execution Environment (MExE) specification for application delivery on next generation mobile terminals.
The intent of the MID Profile was to fine-tune the API´s requirement to support Java on handsets, pagers, and PDAs. The MID Profile was based on the JavaPhone, Java Telephony API, and Mobile Network Computer Reference (MNCR) specifications, which were developed for the PersonalJava™ platform, and thus too large. The new spec better represents the requirements for "state of the art" wireless APIs, such as a display toolkit for limited size and depth displays, user input methods, persistent storage, messaging, networking, security, and wireless telephony.
Mobile phone OEMs see the potential of using Java to access millions of mobile Internet applications through the J2ME architecture. It lets them leverage their manufacturing capability, rather than trying to rally application developers around a proprietary architecture. The attraction of the KVM is that it is scalable to both high and low-end phones. It also provides a means to build and securely deploy new applications and dynamic, interactive content to cell phones and mobile devices."
Regards
JC. |
