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] Downloading ad-hoc Atlas measurements as JSON
- Previous message (by thread): [atlas] [] Downloading ad-hoc Atlas measurements as JSON
- Next message (by thread): [atlas] Ripe-Atlas 500 Internal Server Error ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Thu Sep 24 08:28:44 CEST 2015
On 2015-09-23 15:05, Colin Johnston wrote: >> On 23 Sep 2015, at 14:04, Iñigo Ortiz de Urbina <inigo at infornografia.net> wrote: >> >> On Wed, Sep 23, 2015 at 2:58 PM, Robert Kisteleki <robert at ripe.net> wrote: >>> FYI: this has just been deployed. >> >> RIPE-Atlas-measurement-{{ id }}.json. >> Works for me! :-) >> > > a dated option like 20150923 would be nice as well > > Colin Colin, can you explain what is your use case here? Such naming only really affects downloads via the web page / browser; when using the API one can easily choose a suitable download filename. We could add the end time as well, not just the start time, and we can choose unix timestamps vs. ISO times. All this is pretty simple, but I'd really like to avoid religious wars about how exactly to do this :) Regards, Robert
- Previous message (by thread): [atlas] [] Downloading ad-hoc Atlas measurements as JSON
- Next message (by thread): [atlas] Ripe-Atlas 500 Internal Server Error ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]