Hi,
The current Xindice server package should really have been viewed as just one possible packaging of the Xindice database engine. I'm curious does anyone else agree with this?
I totally agree!
My company is developing an XML-based content management framework, and we are planning to use XIndice as the main store (as it becomes more mature), and we would like to deploy our solutions using XIndice both as an embedded DB, and as a server-based db, depending on the specific needs.
IMHO the best solution would be an XML:DB implementation for the embedded database, so we could easily switch to the network-based one.
Is is wise to start developing such implementation now, or would you suggest to wait until the internal API gets refactored?
So then the question becomes what is the API people use to build applications? To this point we've always used the XML:DB API for this purpose, at least for Java developers. If your question is whether or not we should continue to do that? Then that is something I've been wondering too.
I think the XML:DB API is a good place to start, and it is also (potentially) extensible. (I work mainly in java).
I agree that XML database are missing a query language that supports "linking" and "relations".
Francesco
- Francesco Bellomi "Use truth to show illusion, and illusion to show truth."
