Vladimir R. Bossicard wrote:
Currently Xindice only uses B-tree filer but you can define another one in the .xml file: but the value is never used. :-)
We will hopefully fix this problem for 2.0
My personal goal is to make Xindice as modular as possible and let people freely implement features like accessors, filers... It would be absolutely great if academic people could have the possibility to enhance Xindice. A project could be "comparison of several b-tree implementations for Xindice" or "adding security to xupdate/xpath queries for Xindice"...
I don't know if this is realistic, but a modular implementation would be a first step in that direction.
Big +1. My only concern is performance: I'm afraid that too much modularity might affect speed and scalability. Modularity means interfaces, interfaces mean contracts, which in turn mean constraints. I wouldn't want to end up with a rock-solid and lighting-fast indexing engine that has to go through DOM to communicate with the other pieces of the picture. The idea is fine to me, but we have to be *really* careful in designing the "communication protocol" between the various, pluggable, components.
Do you have any particular idea in mind?
Ciao,
-- Gianugo Rabellino
