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] Convert json traceroute output to normal traceroutes.
- Previous message (by thread): [atlas] Convert json traceroute output to normal traceroutes.
- Next message (by thread): [atlas] Convert json traceroute output to normal traceroutes.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Wed Oct 10 11:41:54 CEST 2012
On 10.10.2012, at 9:46 , Stephane Bortzmeyer wrote: > On Tue, Oct 09, 2012 at 09:17:54PM +0200, > Jan Hugo Prins <jprins at betterbe.com> wrote > a message of 111 lines which said: > >> Because I'm a little more used to reading regular traceroute output >> instead of JSON files, > > It would be better if Atlas used the standard structured format for > traceroute output, RFC 5388. Stephane, my experts tell me that the the size of RFC5388 output would be several times that of the json we generate while the json can be easily translated into the XML. So it appears to me that a script that turns the json into the XML would be proper engineering here. If there are many people wanting RFC5388 output we will put it on the to-do list. Daniel
- Previous message (by thread): [atlas] Convert json traceroute output to normal traceroutes.
- Next message (by thread): [atlas] Convert json traceroute output to normal traceroutes.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]