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.
We had to give up on it when we realised that the app state was
growing large and dialup users would have spent WAY too long
downloading the page.
--
Jeff Watkins
http://newburyportion.com/
"Daddy, I want a purple iMac. And I want ice cream!"
-- Unidentified 7-year-old to his father.
