Kimbro Staken wrote: > I understand completely if you're confused. Again this is why I really > wish we had originally packaged this as an embedded database. In that > scenario it would be much clearer what is the database and what is really > an add on component that provides a particular service. Really everything > like the CORBA API, XML-RPC API, XML:DB API, command line tools and all > that are just add ons. People should be building whatever add ons they > want and shouldn't be concerned with whether or not the core project > codifies them as the "official" way. 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 do agree. I find my own attempts to look through the code are hindered by confusion over what's necessary and what's extra stuff on top that I can use or ignore according to my application's needs. Also, since only the XML:DB API is really documented in the Developer documentation, it's hard to know how to use Xindice "raw", or even to know whether it's wise to do so. > Kimbro Staken > Java and XML Software, Consulting and Writing http://www.xmldatabases.org/ > Apache Xindice native XML database http://xml.apache.org/xindice > XML:DB Initiative http://www.xmldb.org >
