David Stanek wrote: > On 1/8/06, Cliff Wells <[EMAIL PROTECTED]> wrote: > > > > > > One of the interesting things (I've heard) about ASP.NET is that it > > never uses cookies. Instead all requests are POST requests that > > resubmit the "cookie". While this seems a bit overkill, it neatly > > solves a lot of issues wrt browsers and cookies. I can't speak for Kid, > > but with Stan at least, implementing this is as easy as redefining the > > "a" tag to flatten to a form with an onClick attribute. > > > > > Interesting indeed. I'm gonna go check out that site later to see what they > are doing. Another approach would be to have Javascript catch clicks to > anchor tags and rewrite a GET request. > > That is definitely thought provoking. As far as I know, they use an "in page" session. That is serialized(pickle) the session info(as many as the developer like) and stores in every returned page(and post them back using tricks mentioned above). Using it right, it is quite nice but it can also bloat the page(I have seen tens of K).
However, I don't know if that meets Jeff's requirement of refreshing and it never expire. For example, if I have 2 tabs each pointing to some page of my site app, frequently using one tab would make sure it never expires and puts no extra load on the system(no in memory session, no db update) but the other tab doesn't know about this and would expire that can give the user odd experience.
