This is a move toward building a reasonable environment for web apps, not "typical websites". A web app wants full control of user interaction, in the same way that a client-server app or desktop app wants full control.
Think of the classic problem: "I logged in to my online banking site, did some stuff, didn't log out, navigated to a few other sites, and walked away from the PC. Somebody came along and used the Back button to back into my online banking site, where I was still logged in...."
What's wrong with this scenario (other than a brain-dead user)? The fact that the user could navigate away without logging out of the app or closing the window (with the effect of logging out). That's the role that Prism plays.
Slashdot Mirror
This is a move toward building a reasonable environment for web apps, not "typical websites". A web app wants full control of user interaction, in the same way that a client-server app or desktop app wants full control. Think of the classic problem: "I logged in to my online banking site, did some stuff, didn't log out, navigated to a few other sites, and walked away from the PC. Somebody came along and used the Back button to back into my online banking site, where I was still logged in...." What's wrong with this scenario (other than a brain-dead user)? The fact that the user could navigate away without logging out of the app or closing the window (with the effect of logging out). That's the role that Prism plays.