On Sunday 09 November 2003 12:17, Niclas Hedhman wrote: > > > OK, this is a VERY good point. But any Query language or system > > > typically requires a lot of thought to be powerful, yet reasonably easy > > > to implement. Let us discuss that later/separately.
> > (& (objectClass=block) (service=o.a.a.DataStore) (version>1.0) > > (| (container=Merlin) (container=Phoenix) ) ) > > I would like to see you implement that for any type of repository, CVS for > instance? Maybe I wasn't clear enough. For a Query system to work, it is important that; 1. There is a solid user API contract, preferably easy to use. 2. The query implementation for each repository type is reasonably easy to implement. 3. The implementation could pass the query, full or in part, to the server, to lower network activity. This is not a small feat, so I have intentionally left it out for the moment, but I DO recognize that there is a need for it (you can't simply linearly load everything when you are searching for an item). So, what I am saying, the Query discussion will continue beyond my first use-case, i.e. it is a separate use-case and handled accordingly. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
