This week's book giveaway is in the OCAJP 8 forum.
We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line!
See this thread for details.
The moose likes JSF and the fly likes large object graphs inside an HttpSession? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA Java SE 8 Programmer I Study Guide this week in the OCAJP 8 forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "large object graphs inside an HttpSession?" Watch "large object graphs inside an HttpSession?" New topic
Author

large object graphs inside an HttpSession?

jaiswal alok
Greenhorn

Joined: Feb 18, 2005
Posts: 2


Do not store large object graphs inside an HttpSession: If you store the data in the HttpSession as one large object graph, the application server will have to process the entire HttpSession object each time. This forces Java serialization and adds computational overhead. The throughput decreases as the size of the objects stored in the HttpSession increases because of the serialization cost.


I just want to know how Java serialization and adds computational overhead
happens? what is serialization cost.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: large object graphs inside an HttpSession?
 
It's not a secret anymore!