The standard recommendation for paging is to re-execute the search for second and subsequent pages and return the second or subsequent chunk of hits. Would that not work in your case?
An alternative is to read and cache hits from the initial search but that is generally more complex. -- Ian. On Thu, Jan 20, 2011 at 7:36 AM, Clemens Wyss <clemens...@mysign.ch> wrote: > (thanks fort he many answers to my initial lucene question "Best practices > for multiple languages?") > > We shall be confronted with the followong problem: > due to the very dynamic access rules on our content, we shall not be able to > formulate these in/as Filter(s). > Hence we need to first search and then apply the access rules (i.e. security > filter). > What is the best approach to implement paging in this situation? Not to > forget, the "overall context" is a web app ;-) > > Thx for your advices > - Clemens > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
