Hi Reg-devs:
I think this is a somewhat worrying trend. There are an awful lot of
potential queries like this that we're going to want, and I don't think
adding Registry methods is going to be scalable for all of them.
I'd like us to discuss a more general query API at the Registry
interface level, and then at least we'll be able to hide these kinds of
queries in the implementation underneath. Note that this is different
from the idea of "stored" queries in the Registry itself (although we
can potentially use some of the same backend code).
A strawman:
String [] getMatchingPaths(String query); // Use default query type
String [] getMatchingPaths(String query, String queryType);
Example:
paths = registry.getMatchingPaths("media-type EQ " + mediaType);
This assumes a dead-simple query language that would let us do basic
boolean matches across a property-space that we would define (basically
the fields in Resource). All we'd need to do for v1 is ensure that one
or two desired queries would work, but this would protect us from API
changes.
Thoughts?
Thanks,
--Glen
[EMAIL PROTECTED] wrote:
Author: chathura
Date: Thu Jan 10 20:48:58 2008
New Revision: 12124
Log:
Implemented the media type based search as a method of the Registry interface.
Added a test case to test media type based search.
(This test case is commented till the media type search is implemented in the
remote registry)
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
