You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-users@xml.apache.org by Wolfgang Meier <me...@ifs.tu-darmstadt.de> on 2002/11/10 14:23:11 UTC

Re: [Exist-open] xindice vs. eXist, the stable store project

> eXist already contains (uses?) [1] Xindice's code (with credit?) so I 
> don't see why the Xindice's folks should do extra work (like we don't 
> have enough to do) to help the eXist project.

Just to make clear, where code from Xindice is used inside eXist:

For compatibility reasons, I copied Xindice's CollectionManagementService and
DatabaseInstanceManager interfaces to the eXist source tree and implemented
them(those interfaces are extensions to the XMLDB and I don't want to introduce
my own extensions, so I use those provided by Xindice).

Otherwise, eXist uses an old version of the b+-tree and paged file code of
Xindice. This code has been taken from an earlier version of dbXML (for that
reason it is still contained in package org.dbxml.core.filer including the
original references). Since eXist makes heavy use of b+-trees, I made quite
some changes to the original code (e.g. added page buffering, changed some find
methods ...).

Also, eXist adds its own storage layer which contains the code for managing
index data and the DOM (in org.exist.storage.BFile and
org.exist.storage.DOMFile). These classes depend heavily on eXist's indexing
logic, so I suspect it is rather difficult to create a common core here.

> For sure both projects could share work (they both implement the XML:DB 
> API so having common clients would make sense) but questions about 
> licenses should first be resolved.

I have no objections to switch the license if other people on the eXist mailing
list would request a change.

Wolfgang
-- 

Re: [Exist-open] xindice vs. eXist, the stable store project

Posted by "Vladimir R. Bossicard" <vl...@bossicard.com>.
> Obviously, these two concepts 
> can be merged with some effort, but is this an effort that needs to be 
> attempted at this time?  At this early stage in both projects, I would 
> say no, and leave such a decision for a time when the two have matured 
> in their own right.

Xindice must deal with other more urgent issues so I don't think it's 
wise to start looking for convergence right now.  But we can keep an eye 
on eachother.  The license is apparently not a problem so there's 
apparenlty lots of room for collaboration.  Later :-)

-Vladimir

-- 
Vladimir R. Bossicard
www.bossicard.com


Re: [Exist-open] xindice vs. eXist, the stable store project

Posted by Wolfgang Meier <me...@ifs.tu-darmstadt.de>.
I completely agree with your point of view. Thanks,

Wolfgang

> There is also the matter of the overall focus of the two projects.  
> Correct me if I'm wrong, but I've always seen eXist as being something 
> of a persistent DOM implementation (like Excelon), where Xindice is 
> more of a document bag (like Tamino).  Both implementations have their 
> benefits and their weaknesses, but depending on a person's needs, one 
> will want to choose one over the other.  Obviously, these two concepts 
> can be merged with some effort, but is this an effort that needs to be 
> attempted at this time?  At this early stage in both projects, I would 
> say no, and leave such a decision for a time when the two have matured 
> in their own right.
-- 

Re: [Exist-open] xindice vs. eXist, the stable store project

Posted by Tom Bradford <br...@dbxmlgroup.com>.
On Sunday, November 10, 2002, at 06:23  AM, Wolfgang Meier wrote:
>> eXist already contains (uses?) [1] Xindice's code (with credit?) so I
>> don't see why the Xindice's folks should do extra work (like we don't
>> have enough to do) to help the eXist project.
>
> Just to make clear, where code from Xindice is used inside eXist:
> ...
> Also, eXist adds its own storage layer which contains the code for 
> managing
> index data and the DOM (in org.exist.storage.BFile and
> org.exist.storage.DOMFile). These classes depend heavily on eXist's 
> indexing
> logic, so I suspect it is rather difficult to create a common core 
> here.

There is also the matter of the overall focus of the two projects.  
Correct me if I'm wrong, but I've always seen eXist as being something 
of a persistent DOM implementation (like Excelon), where Xindice is 
more of a document bag (like Tamino).  Both implementations have their 
benefits and their weaknesses, but depending on a person's needs, one 
will want to choose one over the other.  Obviously, these two concepts 
can be merged with some effort, but is this an effort that needs to be 
attempted at this time?  At this early stage in both projects, I would 
say no, and leave such a decision for a time when the two have matured 
in their own right.

--
Tom Bradford - http://www.tbradford.org/
CTO - The dbXML Group - http://www.dbxml.com/
Apache Xindice - http://xml.apache.org/xindice


Re: [Exist-open] xindice vs. eXist, the stable store project

Posted by Rob Walker <ro...@softsell.com>.
Wolfgang

> Also, eXist adds its own storage layer which contains the code for managing
> index data and the DOM (in org.exist.storage.BFile and
> org.exist.storage.DOMFile). These classes depend heavily on eXist's indexing
> logic, so I suspect it is rather difficult to create a common core here.

It sounds like you've done some considerable work on eXist - nice job.

> 
> > For sure both projects could share work (they both implement the XML:DB 
> > API so having common clients would make sense) but questions about 
> > licenses should first be resolved.
> 
> I have no objections to switch the license if other people on the eXist mailing
> list would request a change.

Here's what my take would be:

- we're just starting to look at xml/db's - so at the moment we're very much a 
"user" class of eXist and Xindice

- we see great potential in xml databases, so are excited to see and help in 
where either one of these projects could grow 

- over time I could see us becoming an enthusiastic supporter and possible 
developer (we participate as a developer in a minor way in a few other open 
source projects)

What's hard for me from the outside is to figure (a) which platform we base 
our efforts on; and (b) thinking we may end up doing the same work twice, if 
we find we need to switch or use both platforms

So for what my opinion is worth, finding a common compatible license and 
seeing if we could find a way to merge the best of both development lines 
would get a big +1. To me, it seems that both projects could keep their 
identity - but a common core codebase would be cool. 

-- Rob


SoftSell Business Systems, Ltd.
' testing solutions for a changing world '
 
+44 (20) 7488 3470
www.softsell.com
robw@softsell.com