Forgot reply all
Original Message
Subject: Re: Public SPARQL endpoints:managing (mis)-use and
communicating limits to users.
Date: Thu, 18 Apr 2013 23:21:46 +0200
From: Jerven Bolleman
To: Rob Warren
Hi Rob,
There is a fundamental problem with HTTP status codes.
Lets say
On 4/19/13 3:49 AM, Jerven Bolleman wrote:
Forgot reply all
Original Message
Subject: Re: Public SPARQL endpoints:managing (mis)-use and
communicating limits to users.
Date: Thu, 18 Apr 2013 23:21:46 +0200
From: Jerven Bolleman
To: Rob Warren
Hi Rob,
There is a fundament
Hi,
On Fri, Apr 19, 2013 at 11:55 AM, Kingsley Idehen
wrote:
> ...
> If you have OFFSET and LIMIT in use, you can reflect the new state of
> affairs when the next GET is performed i.e, lets say you have OFFSET 20 and
> LIMIT 20, the URL with OFFSET 40 is the request for the next batch of
> result
On 4/19/13 7:04 AM, Leigh Dodds wrote:
Hi,
On Fri, Apr 19, 2013 at 11:55 AM, Kingsley Idehen
wrote:
...
If you have OFFSET and LIMIT in use, you can reflect the new state of
affairs when the next GET is performed i.e, lets say you have OFFSET 20 and
LIMIT 20, the URL with OFFSET 40 is the requ
