Overview changes

[Russ Allbery]

Kiernan, Alex <alexk at demon.net> writes:

> The thing I really had to fix was performance of NEWNEWS - what I've got
> now rocks, but it needs overview changes for me to integrate it cleanly.

That sounds great!

> I'd like to add another parameter to OVopensearch, date, which when not
> zero specifies the lower bound on arrival times which OVsearch will
> return. Right now I've just hacked something in which does a binary
> search to pick the right start location for ov3, but just doing the
> simple loop which was in NEWNEWS will work for overview mechanisms which
> I haven't really thought about.

This by itself doesn't make a lot of sense to me in that I can't see how
the overview interface could support it in a way that would be any faster
than just calling OVopensearch for the full range and then discarding
anything below the lower arrival time bound.  But maybe it's intended for
use in combination with the second one?

> The second one is I'd like to add a direction parameter so I can walk
> backwards through with OVsearch (so I get ARThigh first and ARTlow
> last); again I think all the mechanisms can easily support this (at
> least I think I can see how to do it for buffindexed) - I need this one
> to allow me to reduce the high water mark reported by group to allow me
> to cap the latest article which will be presented.

I'm not sure I understand how this reduces the high water mark; the high
water mark already comes from the overview database.

Could you fill in a few more details?  I'm not managing to picture what
you're doing yet.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.