Duration: 21 minutes
Summary: The main idea today is cookies. HTTP protocol is a stateless protocol. That means it treats every request as a separate request. It does not know to tie these requests to the same user. It is our job as developers to do that. There are some approached to remember users’ requests and one of them is cookies. A cookie is a small text file (max 4096 bytes) written to the user’s browser. In your code you can write that cookie to the browser. Then you can check if that cookie exists you can use the value to continue your logic (for example remembering user’s preferences). There are two types of cookies you can work with: session cookie and persistent cookie. As the name implies, the session cookie is only available for that session (until the user exists the browser session). Persistent cookie is available for as long as you want that time to be (2 days, 5 hours, 3 years…). But remember that users can turn cookies off on their browsers. You need to account for that. Cookies are handy when you are developing an intranet site where you have control on who your users are.
Methodology of the development of example: Good coding standard and simplified design to illustrate the key points.
Technology Used: ASP.NET and Visual Studio 2010
Keyword: ASP.NET 4, Visual Studio 2010, Request, Response, Cookie, Persistent, DateTime, Value, Expires.
See the prices for this post in Mr.Bool Credits System below: