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] Introducing: the new result parsing library (Sagan)
- Previous message (by thread): [atlas] Introducing: the new result parsing library (Sagan)
- Next message (by thread): [atlas] RIPE Atlas use cases and more
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Mon May 26 17:35:46 CEST 2014
On Mon, May 26, 2014 at 05:12:59PM +0200, Daniel Quinn <daniel.quinn at ripe.net> wrote a message of 141 lines which said: > The key is to remember that you need to break up that Great Big File > into separate result blobs, either by looping over a fragmented > file's lines, or by parsing the whole JSON file into memory first > and parsing out each result. OK, thanks, it works now.
- Previous message (by thread): [atlas] Introducing: the new result parsing library (Sagan)
- Next message (by thread): [atlas] RIPE Atlas use cases and more
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]