Hi Daniel,
> -----Original Message-----
> From: Daniel Florey [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 4. Februar 2004 13:39
> To: Slide Developers Mailing List
> Subject: Re: proposal: integrate indexing - search
>
...
> >
> > With the interface you proposed we can come together. To
> stay close at the
> > existing I'd like to use the old interface IndexStore
> (perhaps rename it to
> > Indexer, as it is not really a store). It extends Service,
> so we have the
> > Two Phase Commit stuff.
> >
> > public interface IndexStore extends Service {
> > void index(Uri uri, NodeRevisionDescriptor revisionDescriptor,
> > NodeRevisionContent revisionContent)
> > throws ServiceAccessException;
> >
> > void drop(Uri uri, NodeRevisionDescriptor revisionDescriptor)
> > throws ServiceAccessException;
> >
> > // the ExpressionFactoryStuff (to be defined)
> > }
> >
> > Could you live with that interface? If so, we can decouple
> the discussion,
> > how to trigger the indexer.
>
> I don't see how PropertyIndexer and ContentIndexer can be
> handled with this
> interface. How do we know if content or properties have
> changed?
from the context. In the Parent store we know, if we store properties or content,
different methods are used.
> How do we
> know if index should be inserted or existing index should be updated?
> The information is availble, because we know exactly what is
> going on in a
> transaction but gets lost if this interface is used, isn't it?
If the uri is already indexed, update, if not, create? I'm not really sure, if that is
sufficient, this part of API is old.
> I have not known until today that IndexStore exists so I'll
> have a look at it
> in the next time.
regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
