I thought Xindice only enforced unique document identifiers at the
collection level. What's to stop someone from adding the same document
uuid to another collection?

-Matt

> -----Original Message-----
> From: Sean Kelly [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 12, 2002 11:21 AM
> To: [EMAIL PROTECTED]
> Subject: RE: replication
> 
> That sounds like something similar to what I'm working on: combining
> Xindice
> with JXTA.  The idea is to make a peer-to-peer XML database.
> 
> For my application, globally unique identifiers for documents are
URIs.
> That allows me to use URNs like urn:oid:1.3.1.6.7566... for an
> OID-identified document or urn:uuid:7e1f1218ab800128... for a
> UUID-identified document.
> 
> > -----Original Message-----
> > From: Matt Liotta [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday 12 June 2002 10.52 AM
> > To: [EMAIL PROTECTED]
> > Subject: replication
> >
> >
> > I am not sure if anyone has thought about replication for Xindice,
but I
> > can certainly see some applications for it. One of the first issues
for
> > dealing with replication is obtaining a globablly unique identifier
for
> > each document in the database. As far as I can tell, this can be
simply
> > done by concatenating the unique identifier of the document in a
> > collection with the unique identifier of the collection in the
database.
> > Is this correct?
> >
> > -Matt
> >

Reply via email to