I certainly don't mind if a separate CVS repository is setup and we work with that until we are ready to integrate back with the main Xindice tree. However, it would seem to be useful to share the changes we are making as we make them with this list. If for nothing more than an extra set of eyeballs.
-Matt > -----Original Message----- > From: Vanessa Williams [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 16, 2002 8:24 AM > To: [EMAIL PROTECTED] > Subject: Re: Xindice as a servlet? > > Mark J. Stang wrote: > > > Sure, what do you want to call it on SourceForge? > > I can't think of anything profound. The best I can come up with is Xindice > Embedded. Since it's not going to be a permanent project anyway, it > probably > doesn't matter much what it's called. > > Just so we're clear, looking at a post of yours from Jun 13th, am I > correct > that this is what we're planning to do? > > 1) define interfaces to the "core" of Xindice; > 2) implement the XML:DB API on top of the Xindice core interface. > > Programmers who want to use Xindice embedded can code to the "core" > interfaces, or to XML:DB, whichever they prefer. The XML:DB part has to > have > the server components built-in, as per Kimbro's message, and then the > network layer is gone. Et voila! an embedded Xindice package. > > Is that an accurate description of the project's purpose? > > Cheers, > > Vanessa > > > Mark > > > > Vanessa Williams wrote: > > > >> Are you willing to lead this thing, Mark? > > -- > > Mark J Stang > > Software Architect > > Cybershop Systems > > > >
