File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

A discuss about the place to store search result

 
Bigwood Liu
Ranch Hand
Posts: 240
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In a web application, the user is allowed to search and edit the search result , where should the search result be stored?

1. the search result is personal, and because the result maybe multi-pages which means that to browse the search result multiple request is needed. the session seems a good place to store the search result.

Problem: when big amount of user logged in, and the search result content is huge, the memory is easily eaten up.

If the search result is not stored , search will be carried out every time when you turn the page. this seems not as fast as the session-stored solution.

which is better? stored search result vs. non-stored search result。
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13048
6
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why dont you take an adaptive approach. Cache until a set amount of memory is used up, then search on demand. The Whirlycache open source toolkit is supposed to work well in a servlet environment.

Bill
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic