Hi Steve,

Here are a few WAP pointers...

1.  It's easy to use tclhttpd as a wap server if you add the
    correct mime types:

        text/vnd.wap.wml                .wml
        text/vnd.wap.wmlscript          .wmls
        application/vnd.wap.wmlc        .wmlc
        application/vnd.wap.wmscriptc   .wmlsc
        image/vnd.wap.wbmp              .wbmp

2.  You've almost got the data flow... it is like this:

        web server --> (WML) --> WAP gateway --> (WMLC) --> mobile
network --> WAP phone

    WML files are text (XML) files, WMLC are compiled, binary
    repsentations.  Same for WMLS (wmlscript -- like javascript)
    and WMLSC.

    The WAP gateway is responsible for compiling the WML and
    sending it through the mobile network.  The Nokia gateway
    also does double service as a standard httpd server, and
    has some JSP stuff for helping to serve WML files.

3.  Of course, tcl-xml is a great asset! :-)

I've got some interesting WAP services running in our testbed,
and will soon have some prototype services running outside.
I prototyped one service (automated stock information) using
SMS.  It's been popular with a lot of people over here... if
you're interested I've currently got it on www.markharrison.net.

Cheers,
Mark.

--
Mark Harrison                         http://usai.asiainfo.com:8080/
AsiaInfo Computer Networks            [EMAIL PROTECTED]
Beijing, China / Santa Clara, CA      http://www.markharrison.net/


Reply via email to