Wireless Markup Language is a language for presentation of text from Web pages on cell phones and personal digital assistants. WML is part of the Wireless Application Protocol that is being proposed as a standard.
WML Interviews are getting tough these days as the technology grows faster. To get through the WML interview one needs to update him/herself in a regular manner. Having said that, just before the interview, it is very important to have a quick glance of the reputed WML questions and answers to make yourself comfortable during the interview process. This is where DoAnswers.com helps you in renewing yourself on WML and various other technologies interview preparation.
11. What is the difference between WML and HDML and which language should I use to develop my application?
Refer to the technical note: Choosing a Markup Language.
12. What is WTAI, and how is it implemented?
WTAI (Wireless Telephony Application Interface) is part of the specification as set out by the WAP Forum (however this is an optional part of the spec). No phone currently fully implements the WTAI library. The Mobile Browser does however implement the make call function of the library to allow the dialling of a number using WML. Using a "go task with a special url" means that the phone can switch from browser to voice mode and dial a call. As this is an optional part of the WAP spec not all browsers support it. For example the Phone.com, Eriscsson and Mitsubishi (Trium) browsers all support this WTAI function but the Nokia browser does not. The Nokia browser examines the wml code and provides a "use number" option for anything that it thinks looks like a phone number (the number could of course be a social security number which would limit the usefulness of this browser implementation) This is an example of the wml code that will dial a voice call:
13. What WMLScript libraries does the Openwave browser support?
Openwave browsers support the WAP-194-WMLScript Standard Libraries Specification. Please refer to the following location for a technical specification. http://www.wapforum.org/tech/documents/WAP-194-WMLScriptLibs-20000324-a.pdf
14. Where 1234567890 is the phone number. The http Get method does not transcode non-ASCII characters, how do I resolve this?
A limitation exists when using the http GET method to encode non-ASCII characters. Non-ASCII characters which are passed in a URL string using the Get method will not be transcoded correctly. This is due to a limitation with HTTP GET request that it does not contain charset infomation and it is not an Openwave platform problem. Due to the nature of this problem, it is impossible for Openwave to provide a work around for this. As a resolution, the POST method should be used instead because this method allows you to specify the charset.
15. Why am I getting "Access Control Error" when I try to access my site from a real phone? It works fine with the Simulator.
This problem is common with newly developed HDML applications. By default, the access control path for an HDML deck is limited to the current domain, in other words the deck is "private". When you access your deck from the Simulator, the request comes from the same domain as the location of your deck (usually your local machine). When you use a real phone, the domain of the card that linked to your deck could be some other domain. To make your deck public, you need to either speicfy PUBLIC=TRUE or MARKABLE=TRUE in the HDML declaration: In WML, all decks are public by default, but can be set to private on a per-deck basis using the "access" tag. For more information about deck access control, please refer to Chapter 6 of the SDK Developer's Guide.
16. Why can't I override the "options" soft key (SOFT1) when an input field is displayed?
The "options" soft key (aka "SOFT1" for HDML) is reserved by the Mobile Browser when an input field is displayed. The browser takes control of this action so that it can present the "text entry mode" function. Users can toggle the current text entry mode by pressing the "options" key on the phone, and the display label changes to indicate the current mode. If you need to present multiple functions when an input field is displayed, the recommended approach is to group all of the functions in a separate menu card, where each function is defined by a separate item in the menu. Provide a link to the menu card as follows: WML < do type="accept" label="Menu"> < go href="#menucard"/> < /do> HDML < ACTION TYPE="ACCEPT" LABEL="Menu" TASK="GO" DEST="#menucard">
17. Why does the Mobile Access Gateway Messenger service return HTTP status code 204 when the notification request succeeded?
If the Mobile Access Gateway Messenger's response to an Add or Delete Notification request is successful, the Messenger responds with status code 204 ('No Content'); otherwise, a specific error response is constructed. The 'No Content' refers to the fact that no content is returned in the response to the HTTP POST operation. While status 201 ('Created') might seem more appropriate for Add requests, this is actually not the case, since the Messenger does not return an entity body containing a URL by which the newly-added notification can be referenced (see Section 8.3 of RFC 1945).