aspose file tools*
The moose likes Servlets and the fly likes A discuss about the place to store search result Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "A discuss about the place to store search result" Watch "A discuss about the place to store search result" New topic
Author

A discuss about the place to store search result

Bigwood Liu
Ranch Hand

Joined: Feb 26, 2003
Posts: 240
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

Joined: Mar 22, 2000
Posts: 12769
    
    5
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
 
Don't get me started about those stupid light bulbs.
 
subject: A discuss about the place to store search result