Abstract
Back in Chapter 1, we discussed the particularities of web applications and the stateless nature of the HTTP protocol. Every time a page is requested, the server processes it, returns it to the client, and completely forgets about it. The same happens on the client side: every page received is a completely new one, even if it comes from the same URL after a postback, for example. It’s immediately evident that if you want to keep some information about the current users while they use the application—login information, selected items in a shopping basket, preferences about the site, filled form fields, selected values, and so on—you need some sort of mechanism from ASP.NET or HTML itself, as HTTP (the protocol) doesn’t provide one.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2004 Daniel Cazzulino, Victor Garcia Aprea, James Greenwood, Chris Hart
About this chapter
Cite this chapter
Cazzulino, D., Aprea, V.G., Greenwood, J., Hart, C. (2004). ASP.NET State Management. In: Beginning Visual Web Programming in C#: From Novice to Professional. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-0728-3_6
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0728-3_6
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-59059-361-5
Online ISBN: 978-1-4302-0728-3
eBook Packages: Springer Book Archive