【正文】 　　Synchronization　　Consider whether you want to support overtheair synchronization, cradled synchronization, or both. Because synchronization will often involve sensitive data, consider how to secure your synchronization data, especially when synchronizing over the air. Design your synchronization to handle connection interruptions gracefully, either by canceling the operation or by allowing it to resume when a connection bees available. Merge replication allows both uploadonly and bidirectional synchronization and is a good choice for infrastructures utilizing newer versions of SQL Server. Consider the Microsoft Sync Framework as it can provide robust synchronization services in a wide variety of situations.Consider the following guidelines when designing synchronization:　　? Design for recovery when synchronization is reset, and decide how to manage synchronization conflicts.　　? If you must support bidirectional synchronization to SQL Server, consider using merge replication synchronization. Remember that merge synchronization will synchronize all of the data in the merge set, which may require additional network bandwidth and can impact performance.　　? If your users must synchronize data when away from the office, consider including overtheair synchronization in your design.　　? If your users will be synchronizing with a host PC, consider including cradled synchronization in your design.　　? Consider storeandforward synchronization using WCF ?！　?如果選擇使3G通信協(xié)議，EDGE協(xié)議相比，速度增快同時，考慮耗費更能量。　　?通過空接口傳送數(shù)據(jù)時，設計合理通信服務傳送最少數(shù)據(jù)量?！　?設備不使或不需時，能夠使得設備部分停止工作?！　?考慮推遲不必無線通信，直設備由部供電時才進行。　　設計功耗時候，考慮以指方針：　　?節(jié)約電池電量，當應程序臺運行時，不更新UI。如果話，以選擇那些能夠從USB或其類型數(shù)據(jù)連接線電設備。Power　　Power is the most limiting factor for a mobile device. All design decisions should at take into account how much power the device consumes and its effect on overall battery life. If you have a choice in devices, consider devices that can draw power from Universal Serial Bus (USB) or other types of data hookups. Research munication protocols for their power consumption.　　Consider the following guidelines when designing for power consumption:　　? To conserve battery life, do not update the UI while the application is in the background.　　? Choose munication methods considering both power usage as well as network speed.　　? Consider deferring nonessential wireless munications until the device is under external power.　　? Implement power profiles to increase performance when the device is plugged into external power and not charging its battery.　　? Design so that parts of the devices can be powered down when not in use, or when not required. Common examples are screen backlighting, hard drives, GPS functions, speakers, and wireless munications.　　? Design services and munications to transfer the smallest number of bytes possible over the air. Choose protocols, design service interfaces, and batch munications with this goal in mind.　　? If you are considering using the 3G hardware munications protocol, consider that while it is significantly faster, it also currently uses much more power than its predecessors, such as the Edge protocol. When you are using 3G, be sure to municate in batched bursts and to shut down munication at times when it is not needed.功耗　　于個移動設備說，電量最受制約個因素。移動所支持API、存UI都不樣。以Visual Studio桌面項目移動項目進行關(guān)聯(lián)，幫助解們間哪些以移植。Smartphone代碼移植Pocket PC去時，Microsoft Visual Studio174?！　?研究并利工具幫助移植工作。　　?如果移植個富Internet應客戶端，那么就好好研究，哪些代碼以不加修改，就移植過?！　?如果移植個網(wǎng)絡應移動設備，那就考慮重UI部分，因移動設備界面。現(xiàn)有應移植移動時，考慮以指方針：　　?如果移植個桌面富客戶端應，那么就全盤重新代碼。有些比較容易，有些難度比較?！　orting　　Developers often want to port part or all of an existing application to a mobile device. Certain types of applications will be easier to port than others, and it is unlikely that you will be able to port the code directly without modification.　　Consider the following guidelines when designing to port your existing application to a mobile device:　　? If you are porting a rich client application from the desktop, rewrite the application in its entirety. Rich clients are rarely designed to suit a small screen size and limited memory and disk resources.　　? If you are porting a Web application to a mobile device, consider rewriting the UI for the smaller screen size. Also, consider munication limitations and interface chattiness as these can translate into increased power usage and connection costs for the user.　　? If you are porting an RIA client, research details to discover which code will port without modification. Consult the technology considerations section of this chapter for specific advice.　　? Research and utilize tools to assist in porting. For example, JavatoC++ convertors are available. When converting from Smartphone to Pocket PC code, Microsoft Visual Studio174?！　?考慮哪些構(gòu)成設備異常活動或疑活動，記錄這些場景日志。參考Technology Considerations節(jié)關(guān)于Mobile Device Manager需求部分?！　?設備數(shù)據(jù)庫日志服務器數(shù)據(jù)庫保持同步，以維持服務器端審核能力。需注意，OpenNetCF基于XML，比簡單二進制日志模型占更存儲空間。Windows Mobile沒有系統(tǒng)事日志。考慮那些日志必須產(chǎn)生設備，網(wǎng)絡連接時，們同步服務器。當設備被設計個基礎架構(gòu)部分時，那么基礎架構(gòu)這層追蹤部分設備活動。 for example, attempted intrusion into the device. When devices are designed to be a part of a larger infrastructure, choose to track most device activity at the infrastructure level. Generally, auditing is considered most authoritative if the audits are generated at the precise time of resource access, and by the same routines that access the resource. Consider the fact that some of the logs might have to be generated on the device and must be synchronized with the server during periods of network connectivity.　　日志　　由于移動設備存限制，應該只必須做日志記錄?！　?設計個合理日志消息提醒策略，不至于暴露重誤異常敏感信息?！　?不捕捉異常，除非能夠處理們。?異常發(fā)生，應程序能夠恢復個已知常狀態(tài)。　　Exception Management　　Designing an effective exceptionmanagement strategy is important for the security and reliability of your application. Good exception handling in your mobile application prevents sensitive exception details from being revealed to the user, improves application robustness, and helps to avoid your application being left