> 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.
PGP signature
