In the RealWorld... many applications actually just re-run a search and jump to the appropriate page within the hits.... searching is generally plenty fast enough to alleviate concerns of caching.

However, if you need to cache Hits, you need to be sure to keep around the originating IndexSearcher as well.

A stateful session bean could be used, but I'd opt for a much simpler solution as a first pass, such as the first point of just re-running a search from scratch.

Erik

On Mar 8, 2004, at 2:14 PM, Clandes Tino wrote:

Hi all,
could someone describe his expirience in
implementation of caching, sorting and paging search
results.
Is Stateful Session bean appropriate for this?
My wish is to obtain all search hits only in first
call, and after that, to iterate through Hit
Collection and display cached results.
I have checked SearchBean in contribution section, but
it does not provide real caching and paging.

Regards and thanx in advance!
Milan



        
        
                
___________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to