why is j2me midp superior to wap?
J2ME MIDP addresses many of the limitations of WAP.
Developed through the Java Community Process (JCP) program under the guidance of an expert group composed of twenty companies representing the wireless industry, J2ME MIDP addresses programming issues most relevant to mobile clients, such as user interface, networking, persistent storage and application model.
Compared to WAP solutions, J2ME MIDP provides the following advantages.
Lower network usage and sever load
In a WAP solution, the server is responsible for generating display markup. This requires a round-trip every time the interface changes. In contrast, a J2ME MIDP client's interface is contained within the device, so it can operate even when disconnected. On occasions when the devices does interact with the server, it incurs less network traffic, because it downloads only application data, as opposed to application data plus interface markup.
Better user experience
WAP markup langauges such as WML are, by design, restricted in the types of interactions they can offer. With the MIDP GUI APIs, it is easy to implement customised widgets and event-handling, opening up unlimited possibilities for mobile client interfaces that are easier and more interesting to use.