WAP 与 XHTML-MP

发布于 2024-07-18 11:01:00 字数 629 浏览 11 评论 0原文

去年我们使用WAP和ASP.NET作为服务器端开发了内联网网站,该网站已经投入生产并被认为是成功的。 我们使用内置 Openwave 版本 6 的低端手机。

现在我们使用 XHTML-MP 更新应用程序,因为我们认为这将是未来支持的移动应用程序技术。 但表现却非常差。 我们在同一时间和同一模块上测试了这两个应用程序,新应用程序比旧应用程序长 10 秒(平均)。 我们消除了几种可能性,例如重定向,并且我们已经压缩了页面(两个应用程序都是 2 kb 大小)。 在测试过程中,我们遇到XHTML-MP应用程序经常出现网络错误,例如“无法解析主机名”和“请求超时”,但在使用相同设备和浏览器的WAP应用程序上却没有。 该应用程序使用相同的代理。 我们测试了使用直接访问和使用代理(WAP 网关)的情况。

我们在应用程序中放置了记录器,用于跟踪应用程序在服务器时间内执行的时间,不到一秒。

我们已经为此投入了大量的时间和金钱,但我们无法弄清楚问题的原因是什么。

这是否意味着在 Openwave 浏览器上渲染 XHTML-MP 的时间比渲染 WAP 的时间长? 为什么我在互联网上没有看到任何提到这一点的文档? 是否建议使用 XHTML-MP 开发新的网络移动设备?

非常感谢任何帮助和建议。

乌辛

Last year we develop intranet web site using WAP and ASP.NET for server side, the site was already on production and was considered successful. We use low end handset which had built in Openwave version 6.

Now we update the application using XHTML-MP, because we think this will be the future mobile application technology that will be supported. But the performance was very worse. We tested both application on same time and same module, the new application is 10 seconds (average) longer than the old one. We eliminate several possibility such as redirect and we already compress the page (both application pare are 2 kb size). During the test, we encountered the XHTML-MP application often get network error, such "Cannot resolve host name" and "Request Time Out", but not on the WAP application using the same device and browser. The application use the same proxy. We tested both using the direct access and using proxy (WAP Gateway).

We put logger in our application that track how long application was executed in server time, and it was less than a seconds.

We already invest so much time and money on this, but we can't figure out what is the cause of problem.

Does this mean that rendering XHTML-MP was longer than rendering WAP on Openwave browser? And why I haven't see any documents on Internet that mention about this? Is developing new web mobile using XHTML-MP are suggested?

Any help and suggestion are very appreciate.

ucin

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

予囚 2024-07-25 11:01:00

请问你的css格式是多少? 建议您不要广泛使用 css 来格式化页面,因为许多手机没有足够的能力来处理它(至少几年前是这样)。

May I ask how much css formatting are you doing? It's recommended that you don't use css extensively to format the page since many handsets don't have enough power to process that (at least a few years ago, that was the case).

粉红×色少女 2024-07-25 11:01:00

这显然是特定于设备(或设备范围)的,您能否告诉我们哪些设备难以格式化 xhtml?

如果是这样,是不是就不能向这些旧的麻烦设备显示 WML 了呢? 例如,您可以查看他们的代理字符串来检测输出它们的标记。

This is obviously very device (or device range) specific, could you tell us which devices struggle to format xhtml?

If so, is it not possible to show WML to these old troublesome devices? You could look at their agent string for example to detect what markup to output them.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文