asp.net - WAP vs XHTML-MP -


Last year, we developed the intranet web site for the server side using WAP and ASP.NET, the site already Was on production and it was considered successful We use a low end handset that was built in OpenWav version 6.

Now we update the application using XHTML-MP, because we think it will be future mobile application technology which will be supported. But the performance was very bad. We have tested both applications at the same time and on the same module, the new app is 10 seconds long (average) more than one long, we eliminate many possibilities, such as redirects and we already have the page (Both application pairs are 2 KB size). During the trial, we encountered a XHTML-MP application often receiving network errors, such as "host name can not be resolved" and "request timeout", but not on the WAP application using the same device and browser. Use the same proxy application We have tested both using direct access and proxy (WAP gateway).

We installed logger in our application which shows how long the application was made in the time of the server, and it was less than one second.

We already invest so much time and money on this, but we can not understand what is the cause of the problem.

Does this mean that the rendering of XHLML-MP3 was more than providing WAP on an open browser? And why do not I see any documents on the Internet that mention this?

Can I ask how many CSS formatting are you doing? It is recommended that since you have not formatted the page to use CSS on a large scale, there is not enough power to process on many handsets (at least some years ago, this was the case).


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -