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

[Joe Shaw]

Hi,

On 12/18/07, Mikkel Kamstrup Erlandsen <mikkel.kamstrup at gmail.com> wrote:
> Very valid use case indeed. However I am not sure why Beagle has
> problems delivering more than 100 hits/search.

It's simply the default.  It can be turned up, but that requires using
the Beagle API.

Whether this is something that should be done in our adaptor or
elsewhere is unclear.  Getting more documents requires quite a bit
more memory and CPU, and Beagle doesn't have a "paging" model.  You
get all the hits (asynchronously) up to the maximum number per
backend.

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

I'm not sure I understand, sorry.

Joe