[atlas] Streaming API, endTime parameter is ignored

Hi Roberto,

Our fault, endTime has been deprecated in favour of stopTime** but we didn’t update the documentation correctly. It will be updated with the next deployment, shortly.

If you set an endTime it will be ignored and you will keep getting measurement results.
On the error subscription you should receive a warning asking you to switch to stopTime instead.

Sorry for the inconvenience

** this is because stopTime and endTime were not used consistently before among our APIs/tools. Now everything should be stopTime.

Ciao,
Massimo

> On 10 Feb 2017, at 10:26, Roberto Nunziato <roberto.nunziato at gmail.com> wrote:
> 
> Hello everybody, 
> 
> I am an Italian student and I am working with the RIPE Atlas Streaming API.
> I am trying to replay events that have happened in the past, so I am using
> the optional parameter endTime in the code below. 
> 
> Now, the stream starts at the specified time but it never ends.
> Am I doing anything wrong? Is this a bug?
> 
> var socket = io(“https://atlas-stream.ripe.net <https://atlas-stream.ripe.net/>:443” , {path: “/stream/socket.io <http://socket.io/>”});
> startTime = 1486256400 //05-02-17 h: 01:00GMT	
> endTime = 1486258200 //05-02-17 h: 01:30GMT
> socket.emit(“atlas_subscribe”, {stream_type: “result”, startTime: startTime, endTime: endTime, msm: 1962548});
> 
> Best,
> Roberto Nunziato

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20170210/c8a75fa0/attachment.html>