Scribd
Upload
127 views2 pages

Comparing and Contrasting Wireless Application WAP and J2ME

WAP and J2ME are both open specifications for developing wireless applications, but J2ME applications have more benefits. WAP is a thin-client protocol for handling small amounts of data quickly via wireless networks, whereas J2ME is a development platform specifically for smart applications. While WAP has wider device support, J2ME allows for better user interfaces, less network traffic, local data processing and storage, and end-to-end security without an intermediate gateway. J2ME also makes more efficient use of device resources than WAP.

Uploaded by

thimmu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
127 views2 pages

Comparing and Contrasting Wireless Application WAP and J2ME

WAP and J2ME are both open specifications for developing wireless applications, but J2ME applications have more benefits. WAP is a thin-client protocol for handling small amounts of data quickly via wireless networks, whereas J2ME is a development platform specifically for smart applications. While WAP has wider device support, J2ME allows for better user interfaces, less network traffic, local data processing and storage, and end-to-end security without an intermediate gateway. J2ME also makes more efficient use of device resources than WAP.

Uploaded by

thimmu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Comparing and contrasting Wireless Application WAP/WML and J2ME

Introduction
The Wireless Application Protocol (WAP) is an open specification that addresses wireless network
characteristics by adapting several data-handling approaches already in use by Web protocols, and
introducing new ones, where appropriate, to the special requirements of handheld wireless devices.
The reuse of existing Web technologies eases the development of WAP applications, and makes it
similar to developing HTML-based Web applications since it is browser-based.

Java 2 Micro Edition (J2ME) Mobile Information Device Profile (MIDP). MIDP is also an open
specification that adapts existing technologies such as Java and the Web. Developing MIDP-based
applications (also known as MIDlets) is similar, but not identical, to developing Java Applets in the
sense they share a similar programming model.

Comparison
J2ME applications have more benefits compared to the Wireless Application Protocol (WAP), in
terms of both features and security.

WAP is a thin-client development protocol, whereas J2ME is a development platform specifically for
smart applications.

WAP is much more widely support than J2ME. If While using an archaic phone like my Nokia 6160,
where web browser is present, and WAP 2.0 supports images and XHTML, giving the application
almost everything it needs without any new markup language like WML.

Verizon is not at all supported in J2ME.

In J2ME the user interface is better compared to WAP application.

The network traffic is less in J2ME, and there are possibilities for application extension that
does not exist in WAP.

WAP (Wireless Application Protocol) was designed to allow wireless devices, and their
limited screens and connection speeds, to access Internet and intranet applications. WAP is
an evolving standard but has already built a significant degree of industry support, making it
the standard of choice for delivering and presenting wireless Internet services to the market of
handheld devices.

WAP standardizes access not only for mobile phones but also for PDAs (personal digital
assistants) and pagers. It works with all major wireless networks -- including CDMA (Code
Division Multiple Access), GSM (Global System for Mobile communications), TDMA (Time
Division Multiple Access), and CDPD (cellular digital packet data) -- over circuit-switched,
packet, or Simple Messaging Service and can be built on any operating system, such as
Windows CE, Palm OS, EPOC, and JavaOS.
WAP is good at handling small information like one or two lines of data, and it is quick and
easy for individuals to access.

Java 2 Micro Edition (J2ME) was developed specifically to address the vast consumer space
of small devices, ranging from smart cards to pagers. This space, with its limited memory and
display constraints, has proved to be an ideal environment for Java.

Without a WAP gateway in the middle, J2ME smart applications can provide scalable end-to-end
security from the back end to wireless devices. This will become especially important as the back
end evolves into a message-driven Web-services framework.

J2ME applications can store and process data locally, thereby reducing network traffic. Not only does
this conserve precious wireless bandwidth and reduce latency, it reduces the likelihood that crucial
information will be intercepted or interrupted (e.g., by denial-of-service attacks).

J2ME applications utilize device processing power efficiently. Instead of encrypting everything with
the same key strength regardless of needs, rich clients can establish a comprehensive differentiating
security policy based on the content.

WAP doesn’t suite to browse in far superior environments.

To use superior environments while browsing, you have to go to the server. You This is possible only
with XHTML (but not with WML). Though that’s not bad when dealing with fat pipes, the mobile
networks goes slow.

WML has its own issues, like supporting only bitmap pictures whereas J2ME supports many formats

WAP is not for everyone. Due to its bare-bones nature, WAP benefits individuals with a high
demand for mobility the most.

You might also like