It's really amazing...

I had the same history of struggling through all the suggested solutions
as you described 
in a previous mail. In the end the probably best of all solutions is
also really simplest
(simplicity implies beauty :-)

Do you support multiple, concurrent long hibernate sessions in one http
user session?

I am asking because I was shocked that a really simple hibernate query
with a little number 
of objects already used up around 64kb in the http session. so storing
long  sessions should be 
done _very_ careful. having multiple long sessions can really suck up
your memory.

regards
Peter



-----Ursprüngliche Nachricht-----
Von: Patrick Casey [mailto:[EMAIL PROTECTED] 
Gesendet: Sonntag, 9. Oktober 2005 06:16
An: 'Tapestry users'
Betreff: RE: best strategy for keeping a huge number of web application
contexts



<snip> 

> P.S.: thanks again for the hibernate tip with keeping dao and session 
> together :-)

        I actually got a wee bit more sophisticated with this when I
realized that I could now support three different persistence methods
via the DAO. So now with my DAOs you can choose the persistence
mechanism you want (Detatch and Lock, Key and reload, or Persist
Session) as a flag. 

        I found that by defaulting to key and reload and only using
session persistence for the cases where I actually needed it, I could
really clamp down on my session memory use but still have the session
persistence available when I needed it. Since all access to the object
was encapsulated inside the DAO, I could let the DAO worry about
associating it with a viable session (or fetching it if need be) on
first use.

        So if you're going down that road (and it sounds like you are),
then allowing multiple persistence models in your root DAO instance
might (or might not) help you get something of the best of both worlds.

        --- Pat



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to