Mark J. Stang wrote:
I think the bottom-line is that the embedded version of Xindice is available to build stand-alone applications or other servers. As such, it is
valuable
to many members of the Xindice community. I am very disturbed that
you see a future where it doesn't exist. Like it is a bug you plan to
remove
in the future. IF THAT IS THE CASE SPEAK UP NOW AND I
WILL FIND ANOTHER DB. SO PLAN ON LIVING WITH IT
FOR 1.X, 2.X, ETC. And no, my caps lock key is not stuck
in upper case.
Well, my unlimited ego is very happy to see that you consider me so powerful in this project to remove this feature. :-) But definitely this is not the case. I am only a voice in the Xindice community (and a minority one on this side), and I'm not going to ask to deprecate or remove anything: I always had mixed feelings about this driver, but I didn't -1 it in the past, and I won't in the future: my opinion is that software is an evolving matter, so only a community driven evolution will be able to tell where we'll stand in the future. And more code (and more choices) are always better than less.
Nevertheless, I'll continue to criticize this "feature", since I still have to be given a convincing example of this driver being really useful (it's not really worth discussing, but my point is that the embedded Xindice can be easily used with plain Xindice "native" API, and that what you are trying to do is use a DBMS as a plain DB: stretching a bit the parallel, is like using MySQL when you only need Berkeley DB. If I'll ever have such a need, I'll probably go with Sleepycat dbxml), but if you are using it, it's just OK to me.
This said, I'm also going to support this driver, trying to keep it in sync with the other ones for what will be possible to me. Just don't expect me to be proactive on that particular side.
Fair enough?
Ciao,
-- Gianugo Rabellino
