Hi Stefan, the IndexStore will not be supported in future. It will be replaced by the IndexTrigger as indexing shall be independant from the stores used as you want to search the whole repository even if it is spread across different stores. The LoggingIndexer is an example on how to listen to index events. A real indexer implementation should update the index in the proper way.
Stefan Fromm schrieb:
Hello,
I'm investigating Slide and found a strange implementation of how to listen to events from an indexer. The events are not fired by the IndexStore itself but are reconstructed and then fired by IndexTrigger. For this there is used the LoggingIndexer which is conceptual not an Indexer but rather an IndexListener.
Why aren't there an IndexEvent with the appropriate EventMethods Create, Update and Remove and a IndexListener? Is there a reason why all index events are fired at the end of a transaction and not inside the transaction when they really appear?
The index can be updated in an asynchronous way after transaction commit. You don't want to update the index inside your transaction as this gives much overhead. Another advantage is that you can filter out duplicate events by using event filters. If you are interested in implementing an indexer on top of the event framework I can give you some hints. Regards, Daniel
Little bit confused Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
