Skip to main content

Connected Limited Device Configuration

-

Connected Limited Device Configuration

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

The Connected Limited Device Configuration (CLDC) is a specification of a framework for Java ME applications describing the basic set of libraries and virtual-machine features that must be present in an implementation. The CLDC is combined with one or more profiles to give developers a platform for building applications on embedded devices with very limited resources such as pagers and mobile phones.[1] The CLDC was developed under the Java Community Process as JSR 30[2] (CLDC 1.0) and JSR 139[3] (CLDC 1.1).

Typical requirements[edit]

CLDC is designed for devices that have limited processing power, memory, and graphical capability. Devices typically have the following features:[1]

  • 16-bit or 32-bit CPU with a clock speed of 16 MHz or higher
  • At least 160 KB ROM allocated for the CLDC libraries and virtual machine
  • At least 8 KB total RAM available to the Java platform
  • Low power consumption, often operating on battery power
  • Connectivity to some kind of network, often with a wireless, intermittent connection and limited bandwidth

Noteworthy limitations[edit]

Compared to the Java SE environment, several APIs are absent entirely, and some APIs are altered such that code requires explicit changes to support CLDC. In particular, certain changes aren't just the absence of classes or interfaces, but actually change the signatures of existing classes in the base class library. An example of this is the absence of the Serializable interface, which does not appear in the base class library due to restrictions on reflection usage. All java.lang.* classes which normally implement Serializable do not, therefore, implement this tagging interface.

Other examples of limitations depend on the version being used, as some features were re-introduced with version 1.1 of CLDC.[4]

CLDC 1.0 and 1.1[edit]

  • The Serializable interface is not supported.
  • Parts of the reflection capabilities of the Java standard edition:
  • No finalization. CLDC does not include the Object.finalize() method.
  • Limited error handling. Non-runtime errors are handled by terminating the application or resetting the device.
  • No user-defined class loaders
  • No thread groups or daemon threads.

Profiles[edit]

A profile is a set of APIs that support devices with different capabilities and resources within the CLDC framework to provide a complete Java application environment. There are specific profiles for devices ranging from vending machines to set-top boxes, with the mobile phone profile MIDP being the most prevalent.[5]

Mobile Information Device Profile[edit]

The Mobile Information Device Profile is a profile designed for cell phones. There are two versions of MIDP available, specified in JSR 37[6][7] (MIDP 1.0) and JSR 118[8][9] (MIDP 2.0). Both versions provide an LCD oriented GUI API, with MIDP 2.0 including a basic 2D gaming API. Applications written to use this profile are called MIDlets. Many cell phones come with a MIDP implementation, and it is a popular platform for downloadable cell phone games.[10]

Information Module Profile[edit]

The Information Module Profile is specified in JSR 195[11] and is designed for vending machines, network cards, routers, telephone boxes and other systems with either simple or no display and some form of limited two way network access. Only APIs for application creation, storage, and network access are defined. These are a subset of the javax.microedition.io, rms and midlet packages in MIDP. Siemens mobile and Nokia put forward this specification to the JCP.

DoJa Profile[edit]

The DoJa profile was designed for DoCoMo's i-mode mobile phone by NTT DoCoMo.

Digital Set Top Box Profile[edit]

The Digital Set Top Box profile, specified in JSR 242,[12] is designed for the cable market. Also referred to as OnRamp, this profile is based on a subset of the OpenCable Application Platform (OCAP), which defines a set of APIs for the development of applications for set-top boxes and similar devices. The profile consists of subsets from the CDC Personal Basis Profile including support for AWT, Xlet, file access, and network APIs, as well as several media-related interfaces from OCAP. The whole profile encompassed 31 Java packages and approximately 1500 APIs.[5]

Optional Packages[edit]

The PDA Optional Packages are specified in JSR-75[13] and are designed for PDAs such as Palm or Windows CE devices. The specification defines two independent packages that represent important features found on many PDAs and other mobile devices. These packages are:

  • Personal Information Management (PIM) which gives devices access to personal information management data contained in address books, calendars, and to-do lists.
  • FileConnection (FC) which allows access to file systems and removable storage devices, such as external memory cards.

General APIs[edit]

java.io
A streamlined version of the java.io package found in the standard edition for doing Input/Output operations.
java.lang
Contains classes that are essential to the Java language. This package contains standard java types like Integers and Strings as well as basic exceptions, math functions, system functions, threading and security functions.
java.util
A streamlined version of the java.util collection library. This package contains the collection classes like Vector and Hashtable. It also contains calendar and date class.

See also[edit]

References[edit]

  1. ^ a b CLDC Overview http://java.sun.com/javame/technology/cldc/overview.jsp
  2. ^ JSR 30, CLDC 1.0 http://www.jcp.org/en/jsr/detail?id=30
  3. ^ JSR 139, CLDC 1.1 http://www.jcp.org/en/jsr/detail?id=139
  4. ^ J2ME APIs: Which APIs come from the J2SE Platform? http://developers.sun.com/mobility/midp/articles/api/
  5. ^ a b Summary of CLDC-Based Profiles http://developers.sun.com/mobility/midp/ttips/cldc/
  6. ^ JSR 37, MIDP 1.0 http://www.jcp.org/en/jsr/detail?id=37
  7. ^ MIDP 1.0 API http://java.sun.com/javame/reference/apis/jsr037/
  8. ^ JSR 118, MIDP 2.0 http://www.jcp.org/en/jsr/detail?id=118
  9. ^ MIDP 2.0 API http://java.sun.com/javame/reference/apis/jsr118/
  10. ^ pocketgamer.co.uk mobile platforms feature http://www.pocketgamer.co.uk/r/Mobile/feature.asp?c=1266
  11. ^ JSR 195, Information Module Profile http://www.jcp.org/en/jsr/detail?id=195
  12. ^ JSR 242, Digital Set Top Box Profile http://www.jcp.org/en/jsr/detail?id=242
  13. ^ JSR 75, PDA Optional Packages http://www.jcp.org/en/jsr/detail?id=75

External links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Connected_Limited_Device_Configuration&oldid=1023418459"

Comments

Post a Comment

Popular posts from this blog

Phil Gingrey

-
Image
Phil Gingrey From Wikipedia, the free encyclopedia Jump to navigation Jump to search American politician Phil Gingrey Member of the U.S. House of Representatives from Georgia 's 11th district In office January 3, 2003 – January 3, 2015 Preceded by Bob Barr Succeeded by Barry Loudermilk Member of the Georgia Senate from the 37th district In office 1999–2003 Preceded by Chuck Clay [1] Succeeded by Chuck Clay [2] Personal details Born John Phillip Gingrey ( 1942-07-10 ) July 10, 1942 (age 78) Augusta , Georgia , U.S. Political party Republican Spouse(s) Billie Ayers Children Billy Gannon Phyllis Laura Neill Alma mater Georgia Institute of Technology, Atlanta John Phillip Gingrey (born July 10, 1942) is an American physician and former politician who served as a U.S. Representative for Georgia's 11th congressional district from 2003 to 2015. He is a member of the Republi...
Read more

Advertising in video games

-
Image
Advertising in video games From Wikipedia, the free encyclopedia Jump to navigation Jump to search Marketing phenomenon Part of a series on the Video game industry Development Video game producer Video game developer designer artist programmer tester Video game design level design Video game programming engine AI Video game graphics Video game music Publishing Markets China U.S. Japan South Korea Localization Censorship content rating Piracy Clone Intellectual property protection digital rights management copy protection Distribution and monetization Buy-to-play AAA game Early access Crowdfunding Downloadable content Games as a service cloud gaming Free-to-play Microtransactions In-game currency Loot box gacha Season pass Battle pass Advertising in video games in-game advergame Types Adult game Casual...
Read more

Phelps Dodge

-
Image
Phelps Dodge From Wikipedia, the free encyclopedia Jump to navigation Jump to search Company Phelps Dodge Corporation Type Public Traded as NYSE : PD Industry Mining Founded 1834 Defunct 2007 Fate Friendly takeover Successor Freeport-McMoRan Headquarters Phoenix, Arizona , United States Key people J. Steven Whisler, Chairman & CEO Products Copper Number of employees 15,000 (2006) Phelps Dodge Tower in downtown Phoenix . Phelps Dodge Corporation was an American mining company founded in 1834 as an import-export firm by Anson Greene Phelps and his two sons-in-law William Earle Dodge, Sr. and Daniel James . The latter two ran Phelps, James & Co., the part of the organization based in Liverpool , England . The import-export firm at first exported United States cotton from the Deep South to England, and imported various metals to the US needed for industrialization. With the expansion of the western f...
Read more