Jesse Vitrone wrote:
Thanks for replies all, lots of interesting points, all good to keep in
mind.
I've googled this, but didn't find anything good. Is there a good way
to find out the size of the session? Check the size of the session,
then run through the app to get app my stuff in the session, then check
the size again? I'd like to be able to serialize it, then check the
file size, but if I remember correctly, HttpSession isn't
serializeable. Maybe loop through everything in the session and make a
collection of my own objects and serialize that? Would that give me a
good idea, or would that be inaccurate?
Best way to do it, you probably could do it in a generic way via a
servlet filter pattern. Interesting idea, I must say, have not thought
about adding some kind of session profiler to an app, too much work.
I can watch the size of Tomcat go up, but that includes all that
Hibernate is doing, as well as some other webapps on the same server
that mine interact with, so just the straight Tomcat footprint isn't
telling me too much.
My best guess is to use a profiler against tomcat, if you dont want to
write anything yourself and then locate the session objects.
After a while you get a pretty good feeling about what you can be put
into a session upon your user base anyway.
- Re: session vs request Werner Punz
-