[JDEV] XDB search
Peter Saint-Andre
stpeter at jabber.org
Thu Sep 27 17:46:43 CDT 2001
FWIW, we had a lot of discussion about next-gen XDB at Jabber Inc. a few
months back. The current XDB is not designed to support more granular data
operations such as updating a specific field in your vCard (right now, you
get the whole vCard and then overwrite the whole thing). But to make these
changes, we'd need a major XDB protocol overhaul. That's one reason we
pulled back from the brink of creating a next-gen XDB component (the
variety of "bindings" such as LDAP, SQL, and so on is another -- you need
a layered approach to building this kind of component in any kind of
generalized fashion).
Peter
--
Peter Saint-Andre
email/jabber: stpeter at jabber.org
web: http://www.saint-andre.com/
On 25 Sep 2001, temas wrote:
> Probably referring to me since you used my XDB++, and I think I'm the
> only person to use that so far ;-)
>
> It's still a conceptual thing, and I would love to have design talks
> around it. Anyone really interested in this should probably join the
> jablein dev list. I would also like people to ponder if XPath is
> enough, or if you really need the full and complex XQuery. Just a
> thought.
>
> --temas
>
>
> On Tue, 2001-09-25 at 08:36, Robert Norris wrote:
> > > Duh, I wasn't thinking here. I still need a mechanism to pass to xdb a
> > > search parameter, like the filter to do the search in LDAP, or the actual
> > > e-mail address to search on. Sooo, I pose the same question about adding an
> > > xdb search to the already coded xdb set, and xdb get. Am I the only one
> > > that thinks this would be a good idea? Input from anyone.
> >
> > I thought about doing something like this. The problem is that the XDB
> > is designed as a layer that hides the details of the backend
> > implementation. So what would the search string look like? For LDAP, its
> > a filter. For an SQL backend, it might be a certain SELECT query. There's
> > no easy way to do it without knowing something about the backend.
> >
> > What would be really good, though a significant development effort,
> > would be an implementation of something like XML Query (see
> > http://www.w3.org/XML/Query). I haven't looked into this in any depth,
> > but it is quite interesting. I will do some reading.
> >
> > I am also aware of some new Data Management components (aka XDB++) in
> > the works, though I'm not aware of their capabilities. Perhaps one of
> > the developers on this project would like to give an overview of whats
> > different?
> >
> > Regards,
> > Rob.
>
>
More information about the JDev
mailing list