Jeff Watkins wrote:
On 8 Jan, 2006, at 10:36 pm, [EMAIL PROTECTED] wrote:
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).
You know it's funny how everything old is new again... this is exactly
what we did back in 1995 because our CGI Web application didn't have
sessions and because cookies were so new and feared by the privacy and
security wingnuts.
Yes, but there's a time for everything... Apple Newton versus Palm, OSX
versus NeXT. Bandwidth isn't nearly the issue it once was, so perhaps
this idea's time has come (just because MS got it wrong doesn't mean we
have to) ;-)
Cliff
