Yes, very true. As another data point, I've found another project to use Xindice on, this time as a single-user "embedded" XML store. I just create a Database instance and make calls right to that. Works positively beautifully. I think it's important to make this point. A couple weeks back someone mentioned that they couldn't imagine Xindice being used on the client side, or that using it as anything other than a web service didn't make sense. Can't remember the exact quote. But I can tell you that's incorrect - in fact it works very, very well on the client side.
Sound cool. But I'm not getting why you want to use a Database on an embedded system which mimicks a filesystem. Is there any performance gain against plain filesystem and XPath queries or is it just a matter of "comfort" since everything is already made?
I would go so far as to say, keeping the web services modular would allow the Xindice "core" to be kept very lean, for embedded applications, and then on the server side you can plug in the "service module" of choice: xml-rpc, soap, etc. Whatever suits your needs. That would make this one seriously flexible XML system.
Amen. Makes a lot of sense.
Ciao,
-- Gianugo Rabellino
