On Saturday, May 11, 2002, at 12:51 PM, Stefano Mazzocchi wrote:
This is what I've been saying for a couple months. I don't want to worry about the XML:DB API right now either. I just want to figure out what functionality we want in this area and then see what we do with the API. I'
I have resources to dedicate to metadata, security and versioning, but I don't want to be blocked in the middle of a "XML:DB API" muds. This is my reasons for wrapping instead of patching.
This said, I'm very willing to reconsider this ideas based on what this community finds appropriate... the only thing that is slowly killing the evolution of this project is an API that was created *before* the mile-long TODO design list was written. An API that not many seems to be endorsing.
My suggestion is: forget the API and concentrate on functionality. The API will follow.
ve just been looking to other people to step up and decide what should happen here. I don't have any personal interest in this area (nor the time to really do much right now, hopefully that will change in a month or so).
Once we get a clear picture on what functionality is being exposed by the server, then we can worry about the java API and whether we stick with the XML:DB API or not. In the short term we can just work the functionality at the XML-RPC level.
But I'm pretty sure the xindice committers don't agree with my vision, or am I wrong?
-- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. <[EMAIL PROTECTED]> Friedrich Nietzsche --------------------------------------------------------------------
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
