[Xesam] Need paged search mode for xesam

Jos van den Oever jvdoever at gmail.com
Wed May 7 12:15:49 PDT 2008


2008/5/7 Jamie McCracken <jamie.mccrack at googlemail.com>:
>  I think we would need:
>
>  GetPagedHits
>
>  GetPagedHitData
>
>  to cover all use cases

If you show 10-100 (any number, really) hits at once, you gain very
very little. If GetHitsData is really your bottleneck because you
serialize 98 instead of 2 4 byte integers than you have an amazingly
fast piece of code.
I would think that the amount of work to send 98 ids instead of 2 is
nothing in comparison to serializing the reply to that call. If each
reply contains a uri, a title and a size it's already 100 times as
large as the 4 bytes needed to send the number of the hit you want.

So what we are discussing here is adding to more functions to an API
to get approximately 1% performance gain. This is not worth the added
complexity to the API. Improving the documentation on the current API
makes much more sense.

Even if you want to add two more calls they should not be called
GetPagedHits and GetPagedHitsData but GetRangeHits and
GetRangeHitsData.

Cheers,
Jos


More information about the Xesam mailing list