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。
Author and all-around good cowpoke
posted 8 years ago
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.