> I think I understand your explanations yet I struggle to see how scenario I > was describing is optimization-only. Consider these scenarios: > > Shopping w/o signing in. > 1.I go to amazon.com and fill my shopping cart with stuff without signing > in. > 2.I navigate away to somewhere else and short time later (< HttpSession > timeout) type in 'amazon.com' to go back. At this point I'd still expect to > see my cart's content. > > My Home Page is a portal > 1. My home page is my.yahoo.com. When I launch my browser I get > authenticated via a previously-stored cookie. > 2.During the course of the same browser session I can navigate away to > another site and then hit CTRL+H to go to my home page again. > 3.As I land on my.yahoo.com seems that I am *not* re-authenticated from a > persistent cookie - instead a cookie issued in #1 is used to locate my > server-side state. > > In both of these scenarios NOT retrieving state from steps #1 is not merely > a non-optimization - but > unexpected behavior. Do you agree?
No I don't. This is where bookmarkable pages are meant for. In both cases you would use cookies, and these bookmarkable pages read the cookies to determine what's in the cart. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
