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] feature requests
- Previous message (by thread): [atlas] feature requests
- Next message (by thread): [atlas] feature requests
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Fri Nov 22 11:30:04 CET 2013
Hello, > But anyway. My wishes have been stated a few times now, do what you > want with it. Since this thread is also about quotes: "There's no problem in Computer Science that can't be solved by adding another level of indirection to it" I propose a middle ground here (between "UDMs are immutable" and "I need a stable ID anyway") -- labels. The user specifying a UDM would be able to attach one (ore more?) labels to it, like "Ping to Gert's network". Then this label can be used in access functions, like data downloads, where instead of an ID, you ask for the label; the result is a union of all the measurements with that label. In other words, a label is a kind of ID that stays the same across multiple measurements. Would this work for you? Regards, Robert
- Previous message (by thread): [atlas] feature requests
- Next message (by thread): [atlas] feature requests
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]