Re: Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-06-03 Thread Andy Seaborne
There's a practical tradeoff of streaming and whole result processing in the server. Streaming can give lower latency to first result for the client which can be a better user experience. HTTP status code go in the header so to insert the perfect answer, the server needs to see the end of the

Re: Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-05-31 Thread Kingsley Idehen
On 5/31/13 11:17 AM, Mark Baker wrote: On Thu, May 30, 2013 at 10:33 AM, Kingsley Idehen wrote: On 5/30/13 9:13 AM, Andrea Splendiani wrote: Hi, let me get back to this thread for two reasons. 1) I was wondering whether the report on DBPedia queries cited below was already published. 2) I hav

Re: Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-05-31 Thread Mark Baker
On Thu, May 30, 2013 at 10:33 AM, Kingsley Idehen wrote: > On 5/30/13 9:13 AM, Andrea Splendiani wrote: >> >> Hi, >> >> let me get back to this thread for two reasons. >> 1) I was wondering whether the report on DBPedia queries cited below was >> already published. >> 2) I have recently tried to u

Re: Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-05-30 Thread Kingsley Idehen
On 5/30/13 10:42 AM, Andrea Splendiani wrote: Hi, good. A different http header would be good. The problem is that, in a typical application (or at least some of them) you don't really know which server is there, so specific headers (non http) may not be known. More in general, I think the wi

Re: Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-05-30 Thread Andrea Splendiani
Hi, good. A different http header would be good. The problem is that, in a typical application (or at least some of them) you don't really know which server is there, so specific headers (non http) may not be known. More in general, I think the wider public won't be so precise: either you get

Re: Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-05-30 Thread Kingsley Idehen
On 5/30/13 9:13 AM, Andrea Splendiani wrote: Hi, let me get back to this thread for two reasons. 1) I was wondering whether the report on DBPedia queries cited below was already published. 2) I have recently tried to use DBPedia for some simple computation and I have a problem. Basically a que

Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-05-30 Thread Andrea Splendiani
Hi, let me get back to this thread for two reasons. 1) I was wondering whether the report on DBPedia queries cited below was already published. 2) I have recently tried to use DBPedia for some simple computation and I have a problem. Basically a query for all cities whose population is larger th