This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Streaming API, endTime parameter is ignored
- Previous message (by thread): [atlas] Streaming API, endTime parameter is ignored
- Next message (by thread): [atlas] Streaming API, endTime parameter is ignored
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Massimo Candela
mcandela at ripe.net
Fri Feb 10 10:43:56 CET 2017
Hi Roberto, We are checking your case. You will receive an answer soon. Thanks for your email. 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/6bf8aabf/attachment.html>
- Previous message (by thread): [atlas] Streaming API, endTime parameter is ignored
- Next message (by thread): [atlas] Streaming API, endTime parameter is ignored
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]