Not a bad idea. I just made a trait QueryEngineBackedGraph. You can
extend this trait, implement the "select" and the new "ask" method of
the QueryEngine trait, and reading methods in Graph trait work.
Specifically, contains() delegates to ask(), triplesLike() delegates
to select(), and triples() delegates to triplesLike(). triplesLike
template matching should work as specified in Node.matches(), except
for custom Node=>Boolean functions - this will probably be fixed with
time. Method triplesMatching is not a way to go, it will request all
triples and filter it on the client side.
I just need to test it some more and then I'll commit. Then all you
need to do is implement the select() and ask() against some remoting
service. I've given no thought to the updating methods for now.
Please tell me if you think this is a good strategy.
Hrvoje
http://code.google.com/p/scardf/source/detail?r=219
Any feedback is welcome.
Hrvoje
On Thu, Mar 3, 2011 at 11:21, Hrvoje Simic <hrvoj...@gmail.com> wrote:
> ...