Tuesday, May 31, 2011

MIDP software components

------------------|-------------------|----------------|
| Device | Native |
MIDP Java |specific | Applications |
Applications | java |(Compiled from |
|Applications | C, C++, or |
| | other |
|-------------------| Languages) |
-------------------| Device specific | |
MIDP | API | |
--------------------------------------| |
CLDC | |
-------------------------------------------------------|
Device Operating system |
--------------------------------------------------------

Anatomy of the MIDP application

11:35pm
CDLC 1.1

-java.lang
-java.lang.ref
-java.io
-java.util
-java.microedition.io


MIDP 2.0

-javax.microedition.lcdui
-javax.microedition.lcdui.game
-javax.microedition.media
-javax.microedition.media.control
-javax.microedition.midlet
-javax.microedition.pki
-javax.microedition.rms

Anatomy of the MIDP application

11:26pm: CLDC defines a core of APIs mostly take form the J2SE world. Those include Fundamental language classes in java.lang Stream Classes from java.io and simple collections from java.util .



The generalised network API for CLDC is the java.microedition.io

Monday, May 30, 2011

PDAP - Personal Digital Assistant Profile

1:29: This has become less (almost not) used by the mobile devices manufacturers. very sad about that!!

Personal Basis Profile & Personal Profile

1:23am : Layered on the top of the Foundation profile are the Personal Basis Profile and the Personal Profile.


CDC + Foundation Profile + Personal Basis Profile + Personal Profile

Current Profiles

1:07: The foundation profile is a sepcification for devices that support a rich networked J2ME enviroment.


It does not support the User interface other profiles can be layered on top of the foundation profile for the User Interface support and other functionality.

Profiles - What are profiles??

12:56: A profile is on the top of a configuration adding the APIs and specifications necessary to develop applications for a specific family of devices.

Thursday, May 26, 2011

1:00am Native methods cannot be added at runtime. All native functionality is built into the KVM.


The KVM only includes a subset of the standard bytecode verifier. This means that the task of verifying classes is split between the CLDC device and some external mechanism.This has serious security implications, as we’ll discuss later.

12:55 Because the KVM is of small size it can't do everything that the JVM does in the J2SE world.

KVM - Kilobyes virtual machine

12:52 The KVM is the JVM named that the JVM will be consuming megabytes of data but KVM consumes only Kilobytes

J2ME - Boot camp

12:35Connected, Limited Device Configuration Please note the word Limited. The CLDC is the configuration profile that helps us in configuring the Mobile phones, PDAs that have the very limited memory, very limited processing power and so on.