The best first approach is to simply re-query every time the user goes to a new page, keeping around the query in some for or another (perhaps the expression if you're using QueryParser) and the page number.

If that is fast enough, then you're done!  :)

If it is not, then you could consider caching Hits and your IndexSearcher to re-use when paging.

        Erik


On Sep 21, 2004, at 3:33 PM, Chris Fraschetti wrote:

I was wondering was the best way was to go about returning say
1,000,000 results, divided up into say 50 element sections and then
accessing them via the first 50, second 50, etc etc.

Is there a way to keep the query around so that lucene doesn't need to
search again, or would the search be cached and no delay arise?

Just looking for some ideas and possibly some implementational issues...



--
___________________________________________________
Chris Fraschetti
e [EMAIL PROTECTED]

---------------------------------------------------------------------
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