HTTP is a 'stateless' protocol:
A browser asks for a file.
The server hands over the file.
Server doesn't remember browser next time a file is requested.
Viewstate - like a session variable ('cookie') for the page (default)
ViewState("MyItemName") = "x"
Can be switched on/off for individual controls
Issue with ViewState: SLOW - passes data back with every request
HTTPHander 'intercepts' browser requests, processing them - bounce against cache, fr'instance
Motivate need for state
Viewstate: field settings carried from browser to server, back to browser
Cookies: Hi, Pat! - at the browser
Session: Hi, Pat! - at the server
REQUEST/RESPONSE and Netscape
Cookie examples from your browser
Expiration date to store cookie on disk
Tack caching on to the end of discussion of application state management
Find a BIG example to illustrate time savings with caching