wmlscript with WAP 2.0
Dziugas Baltrunas <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi list, I was quite surprised that some Nokia phones supporting WAP 2.0 does not accept text/vnd.wap.wmlscript content type, but only a compiled version (text/vnd.wap.wmlscriptc). Here is what Nokia FAQ (http://www.forum.nokia.com/main/0,6566,1_1_25_30,00.html#37) says about it: 37. What should be kept in mind when creating WMLScript for TCP/IP stack devices? WMLScript is compiled by the gateway as it is sent to devices with a WAP stack. In order to send WMLScript to a browser with a TCP/IP stack, it must be stored in compiled form (wmlscriptc) on the origin server. Further, the origin server must be configured to recognize a new file extension and associate it with the MIME type application/vnd.wap.wmlscriptc. WMLScript content can be compiled and saved using the Nokia Mobile Internet Toolkit. It means that content servers must place compiled wmlscripts (for example, using Kannel's wmlsc or WAP-wmls perl module) in their wap sites. I came up with the idea that WAP 1.x gateways such as Kannel might be still useful and necessary in WAP 2.0 environments, since WAP 2.0 phones still support compiled wml (application/vnd.wap.wmlc) which often is not offered by WAP 2.0 "gateways" such as Squid proxy or others. Many WAP sites are in WML, so compiled versions would work faster anyway with WAP 2.0 phones. I'd like to ask if there is some roadmap to implement WAP 2.0 functionality to Kannel? I see many such requests in [email protected] and anyway, Kannel already has built-in http client and server, RADIUS acc, map-url can still be useful and so on. Of course, we'll need caching and some other functionality common for http proxies, but this is what is needed to implement. Thanks, Dziugas