WAP vs XHTML-MP
Last year we are developing an intranet website using WAP and ASP.NET for the back end, the site was already in production and was considered a success. We are using a low-numbered phone that was built in Openwave version 6.
We are now updating the application with XHTML-MP because we believe this will be the future mobile application technology that will be supported. But the performance was much worse. We tested both apps at the same time and the same module, the new app is 10 seconds (average) longer than the old one. We're eliminating a few possibilities like redirection and we're already compressing the page (both apps are 2KB in size). During the test, we encountered the XHTML-MP application frequently receiving network errors such as "Unable to resolve hostname" and "Request time", but not in a WAP application using the same device and browser. The application uses the same proxy. We tested both using direct access and using a proxy (WAP Gateway).
We put a logger in our application that keeps track of how long the application has been running during server time and it was less than a second.
We are already investing so much time and money on this, but we cannot understand what is the cause of the problem.
Does this mean XHTML-MP rendering was longer than WAP rendering in the Openwave browser? And why can't I see any documents on the internet that mention this? Is the development of a new web mobile phone proposed using XHTML-MP?
Any help and suggestion is greatly appreciated.
ucin