Posted by : Rhyf Ahmad Wednesday, May 20, 2015

Why is state management such a difficult problem that it requires an entire chapter in a book on programming? In the old days (about 18 years ago), using standard client - server architecture meant using a fat client and a fat server. Perhaps your Visual Basic 6 application could talk to a database. The state was held either on the client - side or in the server - side database.
Typically, you could count on a client having a little bit of memory and a hard drive of its own to manage state. The most important aspect of traditional client/server design, however, was that the client was always connected to the server. It ’ s easy to forget, but HTTP is a stateless protocol. For the most part, a connection is built up and torn down each time a call is made to a remote server. Yes, HTTP 1.1 includes a keep - alive technique that provides optimizations at the TCP level.
Even with these optimizations, the server has no way to determine that subsequent connections came from the same client. Although the Web has the richness of DHTML and Ajax, JavaScript, and HTML 4.0 on the client side, the average high - powered Intel Core Duo with a few gigabytes of RAM is still being used only to render HTML. The fact that such powerful computers on the client side are still so vastly underutilized when it comes to storing state is quite ironic. Additionally, although many individuals have broadband, it is not universally used.
Developers must still respect and pay attention to the dial - up users of the world. When was the last time that your project manager told you that bandwidth was not an issue for your Web application? The ASP.NET concept of a session that is maintained over the statelessness of HTTP is not a new one, and it existed before ASP.NET and even before classic ASP. It is a very effective and elegant way to maintain state. However, a number of different choices are available to you, of which the ASP.NET session is just one. A few subtle changes between ASP.NET 1. x and 2.0/3.5/4 have occurred that are covered in this chapter. The Session object remains as before, but the option to plug in your own session state provider is now available.

Contents:

Your Session State Choices
Understanding the Session Object in ASP.NET
  1. Sessions and the Event Model
  2. Configuring Session State Management
  3. In-Process Session State
  4. Out-of-Process Session State
  5. SQL-Backed Session State
  6. Extending Session State with Other Providers
  7. Cookieless Session State
  8. Choosing the Correct Way to Maintain State

The Application Object
QueryStrings
Cookies
PostBacks and Cross-Page PostBacks
Hidden Fields, ViewState, and ControlState
Using HttpContext.Current.Items for Very Short-Term Storage 



Ebook Preview
Get the ebook now (925 kB)

If the link above doesn't work, try the link below


Mirror: Get the ebook now (925 kB)

Leave a Reply

You can leave a comment to request any article(s), software(s), ebook(s) or report the dead link.
Then I will reply as soon as I can :)

Subscribe to Posts | Subscribe to Comments

Welcome to My Blog

Recent Post

Recent Posts Widget
Instagram

- Copyright © Madriva -Robotic Notes- Powered by Blogger - Designed by Johanes Djogan -