The way modern web applications get around this is by telling the browser to send a small, unique value back to the website with each request - this is known as a HTTP cookie. That means every individual request your browser sends to a web server is a newborn babe, cruelly born into a world that is utterly and completely oblivious to its existence. The HTTP protocol that the web is built on is stateless. I'm not sure either one of these reasons are particularly justifiable.Īs a programmer, I understand why session expiration occurs. I know my bank website zealously logs me out of its web interface if I'm idle for more than five minutes. Most programmers look at these sort of browser session timeouts as a necessary evil - sometimes even as a security "feature". You have to manually log in again, remember what you were doing, then navigate back to where you were and resume your work. What's worse is that you're usually kicked out of whatever page context you were working in. If you're anything like me, the answer is lots. How many times have you returned to your web browser to be greeted by this unpleasant little notification:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |