> WAP application structure
First, you have a web application, so it is quite easy to integrate the WAP service.
You do not have to re-build the original business logic, and if your web applications have layers, It is very convenient to extend to wap.
For our current applications, we can simply think of the mobile migration of Web applications. More is the adjustment on the UI \ ue.
> What standards does WAP adopt?
-- XHTML mobile 1.0 (WAP2.0)
Google mobile
Wap.taobao.com
3g.sina.com.cn
-- Wml1.1
3g.qq.com
Wap.kong.net
3g.sina.com.cn
Compared with some website WAP development. Google's mobile applications are based on XHTML mobile1.0 and are indeed doing well. Many other Wap websites support the wml1.1 and XHTML mobile dual standards.
> Whether to use. Net encapsulation controls or custom WML labels
. Net encapsulates a set of mobile development components. Unfortunately, the mobile development template cannot be found in vs2008 (but mobile development is supported ).. The mobile development control in. Net displays different resolution standards based on the corresponding devices. For example, if Pie access is detected,. Net automatically returns the XHTML mobile1.0 label, and if it is another one (based on specific settings), WML labels can be returned. The advantage is that the corresponding tags are automatically displayed based on the support of the device. From the perspective of development efficiency and accessibility, this is the most convenient. However, from the perspective of WAP site adaptation requirements, the controllability is naturally reduced. Therefore, we finally chose the traditional WML output method for processing. Of course,. Net can also use the force-output WML movement mode. Please refer to this articleArticle
Asp.net force output WML
Http://www.cnblogs.com/pumaboyd/archive/2008/09/19/1293950.html? Updated = 1
> WAP session Problems
The main cause of the session problem is the cookie problem. If a device does not support cookies, the session cannot be used. The server end still needs to know the sessionid requested by the client. From the current webProgramWe can also see that this sessionid is actually stored in the cookie. asp. net2.0 stores ASP. net_sessionid by default. Note that if you have never used a session, the value of sessionid changes. The page changes every time it is refreshed.
In. NET development, Ms considers that the client does not support cookie. Ms saves the sessonid by passing a 24-bit value in the URL.
. NET provides a more friendly URL method. "Autodetect", ASP. net2.0 automatically determines whether the client supports cookies. If not, the sessionid is recorded in the URL. After such processing, the session problem is well solved.
> User logon authentication Problems
How to allow users to log on to the mobile phone by default. This demonstrates how many WAP websites use tokens. Generate a token to log on using this token. Of course, you can exit to clear the token program.
> WAP count statistics
Mobile phones do not have enough support for Javascript. the IMG method can be used. Although "image display" may be disabled by mobile phones
We look forward to Google's support for mobile.
Yahoo statistics is the best one.
51. La can also be used because of image statistics
> WAP Encoding
1: Coding settings for program development. Including webconfig settings and pagecode.
2: The mobile client encoding is related. It can only be obtained through decoding specific codes on the server.
For more information, see my following link.
WAP coding problem 1
WAP coding problem 2
IP address and mobile phone number judgment problems
The mobile phone number is blocked by the service provider. Therefore, you should stop Google and Baidu from getting the mobile phone number under WAP.
Due to the WAP getaway problem, you cannot determine whether the IP can be used for some judgment, such as the city. Based on the test results, IP addresses can be used as cities.
> WAP user habits
1: page turning (simple transposition of the next and previous pages brings convenience to Users)
2: title issues (convenient for users to add to favorites, mobile users cannot continuously click and search)
3: URL saving status (because the cookie is invalid, if you want the user to enter the same page next time, please pay more attention to the URL)