In my previous proposal, I send a collection of all modified revisiondescriptors and revisioncontents to the indexer at the end of a transaction.
-----Original Message----- From: Nick Reddel [mailto:[EMAIL PROTECTED] Sent: Freitag, 23. Januar 2004 13:31 To: 'Slide Developers Mailing List' Subject: Re: Integrate Indexstore and SEARCH (was Indexing store)
Hi Christophe
It looks like our solutions should fit together - I went ahead and did the indexing and search implementations, on the meta-data, while you went with the higher-level api, mostly focussed on the content.
Some things:
-- For some applications (e.g. mine), it's critical that indexing occur
within the transaction [i.e. SEARCH needs to reflect the exact store
state). A flag to indicate synchronous indexing?
Good point! Do you think its enough when the indexer takes part at the two phase commit?
I suppose the best place to call the indexer is NamespaceAccessTokenImpl.commit() - correct ?
Nick , I don't understand, can you explain ?-- Property typing is a must, I think. At least to be able to pull out meaningful date-ordering, etc. I've got two (one rdbms, one non) solutions in mind - I'll run them by you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
