[Xesam] Why is vendor.maxhits read-only?

[Anders Rune Jensen]

On Dec 18, 2007 4:22 PM, Mikkel Kamstrup Erlandsen
<mikkel.kamstrup at gmail.com> wrote:
> > > If you want better responsiveness you probably want to fetch the hits
> > > in smaller batches anyway.
> > >
> > > > I know the current api is optimized for returning results used in a
> > > > page-style. But it's really sad that if you want to use it in another
> > > > way you have to jump through hoops to get it to do that :-)
> > >
> > > It should be possible to do more massive "hit-harvesting" to do
> > > additional bulk analysis like I assume you want.
> > >
> > > If this is hard then it is a "bug" in the spec. If you could outline
> > > you use case a bit more it might shed some light...
> >
> > Lets say I want to migrate from tracker to beagle or the other way
> > around, and I want to write a script that takes all my tags and
> > applies them to the other datastore.
>
> Very valid use case indeed. However I am not sure why Beagle has
> problems delivering more than 100 hits/search.
>
> Perhaps this is something that is of lesser issue when clients use the
> xesam API - because the hit reading is sequential. The doc data can be
> resolved on request since beagled knows how many docs are requested...
> Perhaps a Beagle dev can enlighten us?

It's actually not because beagle can't do it, it's just that there are
no way in xesam to tell beagle to deliver only a specified amount of
results.

-- 
Anders Rune Jensen
http://people.iola.dk/anders/