I am considering caching an array of objects as a Session variable, so that it can persist across page views. I am thinking just 50 elements or so will be enough, with a re-caching hook at the end --which is a nice excuse to play with iterators :-)
Now, I have a couple of questions for all of you webware gurus: 1. Assuming the size of an object is, say, ~512 bytes, at 50 items that's ~25k per session. These days it's not much, but if I get so lucky as to have say, 100 concurrent users, we're talking 2.5MB of RAM, which is not much these days, but the purist in me worries: what happens with hanged sessions, sessions that have been abandoned and are still hanging around, etc? So, I guess my question is, how does WK handle storage of session variables, i.e. transition from in-Ram to .ses files, balancing of resources, etc. 2. How can I eyeball how much memory each object will take? is the size of a pickled representation good enough? (i.e. what happens in RAM to methods of an object, etc?) 3. OT: is there a way to clean up the URL sent to the client? i.e., if a form is sending a massive GET to a servlet, can this servlet take out all the ?a=x&b=y crap ? Thanks in advance, Costas _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
