That's an interesing idea. Except that cookies are usually limited to ~I just created a simple class with 20 integers, 20 floats, and 20 strings of 48 characters each. Pickled, the object was 1358 characters long, and run through zlib.compress, it was all of 382 bytes long. That is an awful lot of data for only taking up less than 10% (compressed) of the available storage in a cookie. Fill a file with 4000 characters and see just how much stuff that is. You could also potentially work out a mechanism so that the object gets split across multiple cookies if it is too large. I don't think any browser has a limit on the number of cookies settable by one site. I have attached my goofy test class, just so you can see what it looked like.
4000 characters on the client. You can't stuff much data into 4000
characters. It'd be pretty neat, however. Care to try to implement it?
;-) If not Jerome, anyone else?
It probably isn't the cleanest solution, but it can certainly be made to work. I think most applications wouldn't even need the compression step. I've never actually used the CSM, just codeit's Session product, so perhaps I am barking up the wrong tree...
--sam
-- --------------------------------------------------------- A lot of things wrong with society today are directly attributable to the fact that the people who make the laws are sexually maladjusted. -- from "I Seem To Be a Verb" by R. Buckminster Fuller, 1970.