Page 86 - DCAP512_WAP_AND_WML
P. 86

WAP & WML




                    Notes


                                     Notes  Users will only ever be one click away from performing a main-path activity. Other
                                     activities will also be reachable in a simple way. This is in sharp contrast with the Nokia 7110.
                                   <do type=”accept”> elements are normally used to support main-path activities. They are also
                                   called ACCEPT buttons. Other activities are supported through <do type=”options”> elements
                                   (OPTION elements).

                                                          Figure 6.2:  OPTION  Element  Example

















                                   If you have a single main-path activity, for example, the best you can do is to associate it with an
                                   ACCEPT button, which is always bound to a softkey (usually mapped to Softkey1). This way,
                                   your users are only one click away from the activity they are most likely to perform.

                                   If you have a single <do type=”option”> element (or OPTION button), this will be mapped to
                                   Softkey2. In the case of multiple OPTION buttons, Softkey2 will display the label menu, which
                                   leads to  a pseudo-card  that allows  you to  select the  option from  a simple  list (similarly  to
                                   Softkey1 on the 7110).
                                   Some UP.Browser phones support three softkeys. In that case, you can afford an ACCEPT task
                                   and two OPTION tasks without the need to go through an extra menu.
                                   In the diagram, you can see softkey1 on the left and softkey2 on the right, but this is not always
                                   the case. Softkeys occupy different positions in different implementations of the UP.Browser.

                                   6.4.2 Why HTML is not used in WAP?

                                   HTML was modeled for high bandwidth; it delivers large data files on dedicated connections.
                                   WML is compact for lower bandwidth pipeline; and therefore sends binary encoded content in
                                   small packets.

                                   Compatibility of WAP with others

                                   In the past, wireless Internet access has been restricted by the capabilities of handheld devices
                                   and wireless networks. WAP utilizes standards such as XML, user datagram protocol (UDP), and
                                   Internet Protocol (IP).
                                   Many of the protocols are based on the Internet standards such as hypertext transfer protocol
                                   (HTTP) and TLS but have been optimized for the unique constraints of the wireless environment
                                   like the following:
                                      Low bandwidth
                                      High latency
                                      Less connection stability


          80                                LOVELY PROFESSIONAL UNIVERSITY
   81   82   83   84   85   86   87   88   89   90   91