[atlas] New release in January, features you asked for...
- Previous message (by thread): [atlas] New release in January, features you asked for...
- Next message (by thread): [atlas] New release in January, features you asked for...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Fri Feb 1 13:45:53 CET 2013
Stephane, On 2013.02.01. 12:44, Stephane Bortzmeyer wrote: > On Fri, Feb 01, 2013 at 11:18:37AM +0100, > Vesna Manojlovic <BECHA at ripe.net> wrote > a message of 27 lines which said: > >> * REST API -- althou in Beta! >> https://atlas.ripe.net/doc/rest > > If I read the documentation correctly, it is only to *read* data. If > so, what's the point? There was already a way to access data (download > the JSON file and parse it) and I regret that it will be deprecated > ("is intended to replace the current ways of programmatically > accessing RIPE Atlas data"). The API is also meant to allow listing measurements ("search"). The same API will make it possible to specify measurements. So, so far there was a way to access data, now there's also a way to access metadata, and a consistent way forward for more interaction with the system. > What is really missing is a way to *run* measurements, specially with > variable parameters (such as the QNAME for DNS UDMs). This is coming. As the article states: "We'll start testing two new features soon: one-off measurements and the measurement specification API to start and stop user-defined measurements. Beta testers will help us adjust these features before we go live with them." Regards, Robert
- Previous message (by thread): [atlas] New release in January, features you asked for...
- Next message (by thread): [atlas] New release in January, features you asked for...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]