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 ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Wed Nov 13 18:01:54 CET 2013
On 13.11.2013, at 15:59 , Gilles Massen <gilles.massen at restena.lu> wrote: > For the second point: if keeping the same ID is not possible, allow to > create a new measurement as an (editable) copy of a previous query > (which would be a desirable feature on its own). I prefer creating a new editable measurement over changing an already defined measurement in any other aspect than ending time. Changing other parameters of a measurement will create confusion in diagnosing problems and will complicate any study of how Atlas is used. Changing the definition of something that is normally intended to be immutable looks like bad style/architecture to me in general. Measurement IDs are not scarce and I am sure Gert can write his scripts in a way that does not require him to keep track of IDs manually. ;-) Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: Message signed with OpenPGP using GPGMail URL: </ripe/mail/archives/ripe-atlas/attachments/20131113/e7a43cc4/attachment.sig>
- Previous message (by thread): [atlas] feature requests
- Next message (by thread): [atlas] feature requests
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]