- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Sun, 2 Nov 2014 13:44:34 +0100
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: public-hydra@w3.org
Hi Kingsley, >>> Regarding the slow query time: I've noticed that the results are >>> "dropping" in. If you do clever visualization this might not hurt as >>> much because you can already start drawing and the user sees some >>> progress happening. (How much sense this makes depends on the result format of course) >> >> That's a *very* interesting remark, because it goes to the core of a new query paradigm. >> Indeed, because the query processing happens locally, results are streaming. >> So even though it might take some time until >> _all_ >> of the results are there, >> you can already start acting on >> _each_ >> of the results as soon as they arrive. >> >> So this means, with a SPARQL endpoint, the workflow is normally: >> - you ask, you wait, you do > > Not with Virtuoso. We were talking about the workflow, the way applications are built, not about Virtuoso or any other type of endpoint. What we said is that most (if not all) applications on top of SPARQL endpoints use them in the traditional “ask, wait do” manner, instead of acting on each results as it comes streaming in. Most of the times, SPARQL endpoints are just so fast that programming self-updating results on the client does not help the user. Since executing SPARQL queries with triple pattern fragment clients is slow, this does make a difference (as our demo SPARQL clients also shows). Best, Ruben
Received on Sunday, 2 November 2014 12:45:08 UTC