Connected Device Configuration (CDC)
Definition - What does Connected Device Configuration (CDC) mean?
As part of the Java Platform Micro Edition (Java ME), the CDC is designed for handheld devices and embedded systems. In particular, it is built for devices having better resources (such as RAM and storage memory) than the devices supported by connected limited device configuration (CLDC). The CDC can work with devices driven by 32-bit microprocessors/controllers with an available 2 MB RAM and 2.5 MB ROM for the Java environment.
Techopedia explains Connected Device Configuration (CDC)
Java ME is provided to developers in the form of API sets known as configurations, profiles, and optional packages. A configuration is the largest of these sets. It caters to a relatively broad range of devices. Profiles cater to a narrower range of devices. Optional packages, on the other hand, are APIs adding functionality to applications and catering to specific technologies.
The CDC’s three sets of APIs do the following:
- The foundation profile: For devices with no GUI. It has a J2SE based library and supports several security optional packages, such as the Java Authentication and Authentication Service, Java Secure Socket Extension, and the Java Cryptography Extension.
- The personal basis profile: Includes foundation profile APIs and is for devices with lightweight GUIs. Some abstract windowing toolkit (AWT) classes are also supported. Applications are based on the Xlet application programming model. Developers who write content for Blu-Ray disks use this profile.
- The personal profile: For high-end mobile devices and already supports a GUI toolkit based on the AWT. All applications built upon this profile are based on the applet programming model.
Other optional packages, which can work on top of the CDC, include:
- The RMI Optional Package: For distributed-application and network communications.
- The JDBC Optional Package: used for connecting to data sources such as spreadsheets, flat files, and relational databases.