• Post Reply Bookmark Topic Watch Topic
  • New Topic

Keep-Alive and performance(memory)  RSS feed

 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I notice alot of developers using the Session to store their beans. With the Keep-Alive abilities of jsf pages, would this be a better alternative? Which approach would be better for a system with serious usage, 1000-3000 users at any given time?
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I really need help making this determination. It really seems as if keep-alive is the better of the two approaches. I am not sure of the performance gain/loss of the serialization process.
 
Tim Holloway
Bartender
Posts: 18531
61
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Keeping data on the server in sessions means that having many users will cause a lot of server memory to be consumed.

However keeping data in the client's browser has problems as well.

1. It can greatly increase the amount of network traffic

2. If you send out sensitive data to the browser and back, it can potentially be spied on and/or altered both in transit and inside the user's browser.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!