On 21 Jan 2004, at 14:57, Wallmer, Martin wrote:
In Domain.xml we could have something like:
<store name="jdbc" classname="org.apache.slide.store.BindingStore">
<nodestore classname="org.apache.slide.store.impl.rdbms.JDBCStore">
<parameter name="driver">com.mysql.jdbc.Driver</parameter>
<parameter name="url">jdbc:mysql://localhost:3306/test?autoReconnect=true</ parameter>
<parameter name="user">wam</parameter>
<parameter name="password"/>
<parameter name="adapter">org.apache.slide.store.impl.rdbms.MySqlRDBMSAdapter</ parameter>
</nodestore>
<securitystore>
<reference store="nodestore"/>
</securitystore>
<lockstore>
<reference store="nodestore"/>
</lockstore>
<revisiondescriptorsstore>
<reference store="nodestore"/>
</revisiondescriptorsstore>
<revisiondescriptorstore>
<reference store="nodestore"/>
</revisiondescriptorstore>
<contentstore classname="org.apache.slide.store.txfile.TxFileContentStore">
<parameter name="rootpath">mysql/store/content</parameter>
<parameter name="workpath">mysql/work/content</parameter>
</contentstore>
<indexer classname="my.lucene.Indexer"/>
<searchengine>
<parameter name="propertySearchClass">my.sql.SearchEngine</parameter>
<parameter name="ContentSearchClass">my.Lucene.SearchEngine</parameter>
</searchengine>
</store>
Does this make sense?
It sure does, but I believe you missed my point.
Here, you are partitioning the tree with stores, and you are associating indexers and searchengines to the store.
What if I want to have two different partitions of the tree space, one for storing and one for indexing/searching? [I believe Oliver was wondering about this as well] and potentially having them layered allowing a single file to be indexed/searched by more than one indexer at the same time?
I think it would be much more flexible than the above, but might be flexibility syndrome alltogether.
What do others think?
-- Stefano.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
