Abstract
No web application framework, no matter how advanced, can change the fact that HTTP is a stateless protocol. After every web request, the client disconnects from the server, and the ASP.NET engine discards the objects that were created for the page. This architecture ensures that web applications can scale up to serve thousands of simultaneous requests without running out of server memory. The drawback is that your code needs to use other techniques to store information between web requests and retrieve it when needed.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2010 Matthew MacDonald, Adam Freeman, and Mario Szpuszta
About this chapter
Cite this chapter
(2010). State Management. In: Pro ASP.NET 4 in C# 2010. Apress. https://doi.org/10.1007/978-1-4302-2530-0_6
Download citation
DOI: https://doi.org/10.1007/978-1-4302-2530-0_6
Publisher Name: Apress
Print ISBN: 978-1-4302-2529-4
Online ISBN: 978-1-4302-2530-0
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)