Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
Session State is a tried and true solution in the ASP.NET Framework for maintaining information for users because we've got a problem here. We've talked about it already, a bunch of times in this course and that is the web server does not see multiple requests as connected or related in any way. However, the end-user does. If I come to your website to buy something, I may fill out a form, order a product or whatever and as I move from page to page, I want to see the things that I've already filled out, carried over to the next page. I don't have to type the same information 14 times, all that sort of thing. So to me as an end-user, I want this to run like a Desktop Application, however the web server doesn't do that. So the solution is that if we're going to keep track of a series of connections and give the end-user this connected Desktop Application type feel, it has to be a deliberate programming action on our part. Now Microsoft has taken care a lot of this by building this functionality into ASP.NET through the .NET Framework and they kind of group all of this functionality together under the heading of Session State Management. Well like I said, this has been around ASP.NET for quite awhile. It's still very, very similar in ASP.NET 4 but you do need to be aware of these and the kind of strengths and weaknesses of each one as you prepare for this exam. This stuff will be on the exam in some form and you'll need to understand it to help you get past the questions alright? Now you have three basic options when you're talking about Session State Management in ASP.NET 4. There's InProcess Storage or InProc Storage, there's State Server and then there's Database Session State Storage. Now when we're talking about a session here, make sure we're on all the same page. When you connect to that web server for the first time, it's says, oh wait a minute I don't think this person's been here before and it creates a SessionID. Now it will then pass this SessionID back and forth between the, the Client and the Server and this is what it uses to check and make sure, oh this person's been here, it kind of uses that as a key to connect to a database to pull more information about what you filled out before or what you did before and this is the magic that makes this application feel like that it's functioning as a Desktop Application. And it makes the user feel important and, and well cared for and it makes the web application seem coherent on the users side. So we'll take a look at these, each one of these three options in a separate video entitled Session State Storage Options, but again, make sure you're aware of these, it wouldn't hurt to go out and do a little bit of reading on each one of these, before you go sit this exam because this will be there. It is a fundamental aspect of designing a web application in ASP.NET 4.
| Course: | Designing and Developing ASP.NET 4 Web Apps (Exam 70-519) |
| Author: | Mark Long |
| SKU: | 34292 |
| ISBN: | 978-1-61866-029-9 |
| Release Date: | 2011-12-31 |
| Duration: | 8.5 hrs / 108 lessons |
| Work Files: |
Yes |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |