simple search api (was Re: mimetype standardisation by testsets)

[James "Doc" Livingston]

On Thu, 2006-12-21 at 19:07 +0100, Jean-Francois Dockes wrote:
> About 2), URI *is* an appropriate handle, and probably the best as long as
> we can't guarantee the stability of the result set (that is: *if* we need
> separate Query() and GetSnippets() calls, *then* the URI is probably the
> best identifier to ensure consistency).

What if the URI of a given item can change? I'm think in particular of
the backends which handle "file got moved" in ways other the simple
"remove old and add new" method.


If you had to retrieve the URI as a property rather than it being a
unique identifier there would still obviously be some issues for things
that are using the simple non-live interface, but potentially having
stale data is what you get from using a non-live query.

Using an old URI as the unique identifier to retrieve other data (like
snippets or something) could lead to some  odd situations.


Cheers,

James "Doc" Livingston
-- 
[Request for the names of the kings who became Nazgul]
Dashur, Daensir, Prantsur, Vicksinn, Comuet, Cupuid, Dondor, Blitsun,
and Rodulf, Witch-King of Angmar. -- Joseph Michael Bay