- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Sun, 3 Aug 2014 15:14:00 +0200
- To: peter@vandenabeele.com
- Cc: "<public-hydra@w3.org>" <public-hydra@w3.org>
Hi Peter, >> FYI The SPARQL client of triple pattern fragments >> no longer looks at a fragment's status code to determine emptiness: >> https://github.com/LinkedDataFragments/Client.js/commit/e2c06d4538 > > > +1 for this commit: > > 6 insertions(+), 31 deletions(-) > > This indicates that the current resolution is simpler (less code, less technical debt). Yes, but it's not entirely fair in this case: the client worked without that code too; it was simply an optimization that saved on bandwidth and processing. The real benefit is visible on the server side: - https://github.com/LinkedDataFragments/Server.js/commit/c2501c041a 2 additions – 13 deletions (JavaScript) - https://github.com/LinkedDataFragments/Server.Java/commit/2e22edd4e 0 additions – 2 deletions (Java) Implementing servers has become simpler, at the cost of one (minimal) optimization that's no longer possible. Best, Ruben
Received on Sunday, 3 August 2014 13:14:33 UTC