Đang chuẩn bị liên kết để tải về tài liệu:
Webmaster's Guide to the Wireless Internet part 34

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Webmaster's Guide to the Wireless Internet part 34. The Webmaster’s Guide to the Wireless Internet provides the Wireless Webmaster with all of the tools necessary to build the next generation Internet. Packed with the essential information they need to design, develop, and secure robust, e-commerce enabled wireless Web sites. This book is written for advanced Webmasters who are experienced with conventional Web site design and are now faced with the challenge of creating sites that fit on the display of a Web enabled phone or PDA | 302 Chapter 7 Deck of Cards Designing Small Viewpoint Content Figure 7.5 Continued p card wml When we load this page into our browser without specifying the mode variable http localhost test.php we can see that the final size of the WAP binary is 187 bytes as shown in Figure 7.6. Figure 7.6 Binary Size without Indexing SELECT List However when we load up the page specifying mode index within the query string http localhost test.php mode index we see that the final size of the binary is 146 bytes.This is illustrated in Figure 7.7. You can see from this example that using indexed SELECT lists can save significant numbers of characters even after the code is parsed by the WAP gateway. The end user will notice absolutely no difference between the two different cards but the indexed card is 22 smaller than the first version. A deck that contains many SELECT lists would benefit greatly from this simple method of saving characters. This implementation should be used with care however as a client-side coder can change the order of the list or alter the display value without confirming the meaning of the variable s actual value with the server-side programmer. www.syngress.com Deck of Cards Designing Small Viewpoint Content Chapter 7 303 Figure 7.7 Binary Size after Indexing SELECT List It is incredibly unlikely that the continents featured in our example will change in our lifetimes and affect our results so you could store this information as part of a user profile without potential errors resulting in the future. However if we were using SELECT lists to denote information that is somewhat likely to change over time such as voting districts or area codes or information that is constantly changing like current movie listings we would need to take very special care to ensure that there is a consistent correspondence between the value of the index and the description of the value that is displayed. One way to do this would be to generate the SELECT list dynamically with .