Section 1: JTWI (JSR 185) And Overview of JTWI-Compliant Wireless Applications
JTWI overview - familiar with wireless applications
-------------------------------------------------- ------------------------------
IDENTIFY THE
Goals and
Characteristics of The JTWI Specification (JSR 185), Including the
Mandatory Specifications,
Conditionally relquired specifications, and the
MINIMUM Configuration. Compare The Relationship and Differences Between JTWI AND Other Wireless Java Technologies.
Master the goals and features of JTWI specifications (including mandatory, conditionally required and minimum configurations). Compare the relationship between JTWI and other wireless Java technology and different points.
Develop portable applications that are compatible with the requirements and restrictions an application programmer must adhere to, in order to ensure compatibility with a JTWI-compliant device, including resource minimums (standard-size application), clock resolution, and the use of preferred Multi- Purpose Internet Mail Extensions (MIME) names as applicable to Connected Limited Device Configuration (CLDC) 1.0 and 1.1, Mobile Information Device Profile (MIDP) 2.0, Wireless Messaging API (WMA) 1.1, and Mobile Media API (MMAPI) 1.1).
Development portable application
-------------------------------------------------- ------------------------------
The goal of the JTWI specification is to improve the compatibility, interoperability and completeness of J2ME technology implementations in mobile phones. The JTWI specification minimizes API fragmentation and raises the bar of functionality for high-volume devices thereby broadening the already substantial base of applications that have BEEN Developed for Mobile Phones.
Objective: Improve compatibility, interoperability, and integrity of J2ME technology on mobile phones. The JTWI specification reduces API differentiation and eliminates functional obstacles.
THIS SPECification Achieves these Goals in Three Ways:
This specification reaches the above objectives through three channels:
_ First, it specifies a common set of APIs by requiring the use of a number of component specifications such as the MIDP Specification version 2.0 (MIDP 2.0). In some cases, these specifications provide uniform access to services that were once only available through device Specific Apis, or not at all. First, it has set a set of public API collections through some sub-specifications, such as: MIDP2.0.
_ Second, IT Mandates Elements of The Component Specifications, The Component Specifications, Thereby Eliminating Optional Features and Improving Compatibility.
Second, it manages the basis of the subscript, eliminating the improvement of the optional characteristics improve compatibility.
_ Third, Some Elements of The Component Specifications Have Been Clarified With Spectation.
Third, some sub-norms have been explained in this specification.
The specification leads of the component specifications (such as MIDP 2.0 or WMA 1.1) have been proactive participants in the JSR-185 expert group and the development of this specification. They have been active in proposing clarifications included in this specification, and they have also Taken Responsibility for Additional Issues That Will Be Resolved Separately In Maintenance Release of The Component Specifications.
