Mark J. Stang wrote:
And not crossing the border between "products". However, I have always felt that it is a MAJOR drawback, that Relational DBs don't have any way of notifying their clients without polling.
There is a fairly simple way around this by proxying all requests to Xindice via a client-side layer which takes care of all the unsupported things like callbacks, metadata, transactions, etc. This is the approach (AFAICT) Dawid and Krzysztof has taken.
This has a lot of advantages - you get all the additional features you want, precisely how you want them. Xindice could have perhaps a basic implementation of these features for those who don't whant to have to write it themselves.
Personally, I'd prefer to see as many superfluous features kept out of the core as possible. I had the mistfortune to work with a particular commercial XML store which did a lot for you (transactions, transformations, persistent DOM, etc), but often the support was incomplete, incorrect or just plain not what I needed for the project. It was extremely frustrating and in the end, caused the project to fail.
Mike.
-- Mike Gratton <[EMAIL PROTECTED]> Leader in leachate production and transmission since 1976. <http://web.vee.net/>
