Relying on nhibernate's second level cache vs pushing objects into asp.net session
Posted
by AhmetC
on Stack Overflow
See other posts from Stack Overflow
or by AhmetC
Published on 2010-04-18T18:51:29Z
Indexed on
2010/04/19
1:13 UTC
Read the original article
Hit count: 384
I have some big entities which are frequently accessed in the same session. For example, in my application there is a reporting page which consist of dynamically generated chart images. For each chart image on this page, the client makes requests to corresponding controller and the controller generates images using some entities. I can either use asp.net's session dictionary for "caching" those entities or rely on nhibernate's second level cache support with using cached queries for example.
What is your opinion?
By the way I will use shared hosting, is nhibernate's second level cache hosting friendly?
Thanks.
© Stack Overflow or respective owner