Upayavira wrote:
Antonio Gallardo wrote:
Could do. How efficient is XIndice? It would need to be pretty efficient on binary data too, as that is our primary use case.Maybe this is a crazy idea but: Is posible to replace jisp with Apache Xindice? Mainly because I have concerns for another ugly move (as jisp did) if we choose a solution from a 3rd party again. If we use Apache Xindice I think this cannot happen again.
Xindice has a Filer abstraction, and there is BTreeFiler implementation. It stores binary objects under an arbitrary binary key, and keys are organized into the BTree for fast store/retrieval. See test for filer here:
http://cvs.apache.org/viewcvs.cgi/xml-xindice/java/tests/src/org/apache/xindice/core/filer/FilerTestBase.java?view=auto
Filer uses several RandomAccessFile descriptors to provide concurrent reads / writes to the file.
Does that answer mean you think a XIndice persistent store implementation would be a good fit? As you're involved heavily in both projects, you'd be the best to comment probably...
Geoff
