SaveAdapterState is called.
Render Render process MobileControl.Render is called, which calls
Adapter.Render. MobileTextWriter is called
to actually output the required markup.
Unload Unload process MobileControl.Unload is called.
Adapter.Unload is called.
Dispose Dispose of
control tree
MobileControl.Dispose is called.
CHAPTER 10 ?– OTHER S ERVER C ONTROLS 509
Figure 10-11. The capability detection and device-specific rendering process
Managing ViewState
Because of varied mobile device display capabilities and limited bandwidth available to mobile
devices, the normal ViewState storage mechanism that uses a hidden form field on the client is
not a viable option.
Instead, the mobile web application stores ViewState data into the Session object. Storing
ViewState in the Session object provides a performance boost, because ViewState is not transmitted
over the wire during each postback cycle. However, this does incur additional memory
demands on the server, which is something to keep in mind when you tune your mobile web
applications.
Once a client device establishes a session with the web application, the session ID is
embedded into the URL of the web application. For example, for the UserControlHost.aspx
page, the client performs the initial HTTP GET with this URL:
http://localhost/ControlsBook2Mobile/ch11/usercontrolhost.
Pages:
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670